> -----Original Message----- > From: Simon Nash [mailto:[email protected]] > Sent: Thursday, October 07, 2010 1:13 PM > To: [email protected] > Subject: Re: [DISCUSS] JIRA categories > > I've added one comment/clarification below. > > Simon > > Florian MOGA wrote: > > Hi, > > > > The Tuscany committers would like to clean up the current JIRA > > categories and would like to find out your opinion about them. > > Currently, we have 2 options: > > > > 1. Reduce the granularity to something like: > > > > Java SCA > > Java SDO > > Java DAS > > C++ SCA > > C++ SDO > > C++ DAS > > OASIS Compliance - OASIS > > OASIS Compliance - TUSCANY > > Tools (including Hudson, Maven, SVN issues) > > Website/Documentation > > Community Ideas > > > > > > 2. Keep a separate category for the most used modules and anything > that > > doesn't fit in any of those can go to something like an SCA Java > > Bindings, SCA Java Implementations or SCA Java Runtime folder. > > > As an example, this would include popular bindings such as binding.ws > and binding.jms. If people have problems with one of these bindings, > it might be helpful if they could quickly search JIRA for problems > specifically related to that binding. Would this be useful? > > Simon
yes, this would help. And it should also be possible to change a category after submission, or submit a bug without category assignment, because sometimes as a user I simply will not know if I'm encountering, say, an SCA or SDO problem. -- Sebastian
