Bob Scheifler wrote:
Mark Brouwer wrote:
I think we should have in JIRA at least the following components:
Website (with or without space)
Infrastructure
Contributions
ServiceUI
JTSK
In Sun's existing issue DB, we use Java package names as the
component granularity for code, and I think it has worked well.
I know Bob and I don't find it very intuitive. I always used 'any' to
browse or search with a proper keyword. For example sometimes I was
curious to see what kind of issues where against the specs, sometimes I
was just interested in implementation details. Going through that pull
down menu to select all the relevant packages was one bridge too far.
Can you also explain the advantage of such a granular level.
For some parts I don't see harm in it (when we consider each net.jini
package a separate spec), but if somebody (also the uninformed user) has
a problem against Outrigger, he or she would like to assign to
Outrigger, the notion of a package name is not very helpful for such a
person.
BTW I expect JTSK to get split in multiple components, but I think it is
nice if we have at least a component for now so we can start. Gregg's
issue is already lingering in the 'unknown'.
--
Mark
