Setting up the issue tracker

Hi folks,

we need to configure the SF issue tracker for our needs. Basically 
there are two option lists to populate: "categories" and "groups" (so 
much for meaningful names).

For categories, I think we should add the components outlined in the 
project charter and then some:

   - WDTE Core
   - WDTE UI
   - WDTE XML Core
   - WDTE XML UI
   - WDTE CSS Core
   - WDTE CSS UI
   - WDTE JavaScript Core
   - WDTE JavaScript UI
   - Infrastructure (Web site, mailing lists, CVS, etc)

Note that I've added the WDTE prefix to the category names here because 
it would make it easier to add sub-projects like JSP tooling later on.

Populating the "groups" option list is less obvious. SourceForge 
suggests "Add groups like 'v1.2', 'unsupported', 'unverified', etc.". 
Obviously groups are issue-tracker-global, so we can't use them to 
further identify modules inside components ("categories"). I think 
pretty much the only thing that makes sense here is version numbers, 
considering that we probably want unified releases including all 
components, and thus the same version numbers across components.

But version numbers is not the same as version numbers :-P. They might 
refer to the version in which the submitter discovered the defect, or 
they might refer to target versions where we intend to have the issue 
fixed/implemented. I think I prefer target versions, but I'm not sure. 
Having the number of the version used by the submitter is very useful, 
but target versions are nice for release management. Any preferences?

Cheers,
Chris

PS: Why is this list so quiet? There was more discussion going on when 
we were abusing the web tools newsgroup than here where we can safely 
discuss everything without being off-topic. I think the number of 
subscribers is currently higher than the number of (non-test) messages 
posted to this list, so at least there are a bunch of people listening 
;-)

--
Christopher Lenz
/=/ cmlenz at gmx.de



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn