#12 hard to manage issues

[Thomas R. Thurman]

Currently there are four issue management systems available for modules:
a-issues.xml in modules directory
b-SEDS on SC4 online
c-bug tracker on sourceforge.net
d-bugzilla (http://www.bugzilla.org/)

a appears to be used primarily by ap239 team

b is used by WG12 as historical record only. The information provided in the document describes the actual action.

c is available for free but the structure of the project makes use of it virtually impossible for anything other than for issues against stepmod itself (like this one!). If the project were restructured into individual projects by part number, (c) would be an easy fit, but taanstafl*.

d has been used successfully by a number of projects for years but is extenal to sourceforge and therefore has the usual problems with management.
The installation instance at NASA has nice organization by standard (e.g., ISO 10303, ISO 8000) part (e.g., 1111, 203, 41) and by publication date.
It has other features that may be of interest as well if we can't adopt the native tracker.

*"There ain't no such thing as a free lunch"-- Heinlein, The Moon is a Harsh Mistress