|Re: [PROJECT] [BUGZILLA] - Dependency Feature [message #8740 is a reply to message #8548]
||Wed, 29 December 2004 02:50
Originally posted by: ilias.lazaridis.com|
> A good showcase of how to _not_ use an Issue-Tracking-System is this one:
> Add early support for J2SE 1.5 features
> this Issue treats with "Cheetah" and many stuff around JSR-176.
> It has around 100 comments and is 1,5 years old.
> I've create the Issue JSR-176, whilst using the dependency-feature of
> JSR-176 J2SE 1.5 (Tiger) Release Contents [100% jck1.5 compliance, ...]
Title, content and scope of this Issue have changed:
JSR-176 J2SE 5.0 (Tiger) Release Contents
Actual dependency tree (focuses mostly on unresolved issues):
you will detect the similarities of the bugzilla dependency-tree and the
According to the plan, "Generics" should be unresolved, too.
Basicly, the plan (and similar plans) should be generated out of the
Bugzilla Plan generation would be an task for the suggested project:
[PROJECT] - Collaboration and Government Infrastructure (CAGI)
This way all eclipse teams can produce up-to-date and in-synch plans
with a minimal effort.
The BIRT project could support this, too.
> A user which searches within bugzilla (e.g. "176" or "Tiger") hits on
> this Issue, and gets immediatly a clear picture (including relations of
> Issues) - just by the Issue-Tracking-System.
Powered by FUDForum
. Page generated in 0.01651 seconds