|
| Re: [PROJECT] [BUGZILLA] - Dependency Feature [message #8740 is a reply to message #8548] |
Wed, 29 December 2004 02:50   |
Eclipse User |
|
|
|
Originally posted by: ilias.lazaridis.com
ilias wrote:
> A good showcase of how to _not_ use an Issue-Tracking-System is this one:
>
> Add early support for J2SE 1.5 features
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=36938
>
> 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
> Bugzilla:
>
> JSR-176 J2SE 1.5 (Tiger) Release Contents [100% jck1.5 compliance, ...]
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=80775
Please note:
Title, content and scope of this Issue have changed:
JSR-176 J2SE 5.0 (Tiger) Release Contents
https://bugs.eclipse.org/bugs/show_bug.cgi?id=80775
Actual dependency tree (focuses mostly on unresolved issues):
https://bugs.eclipse.org/bugs/showdependencytree.cgi?id=8077 5
Actual plan:
http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt- core-home/r3.1/main.html
you will detect the similarities of the bugzilla dependency-tree and the
plan.
According to the plan, "Generics" should be unresolved, too.
-
Basicly, the plan (and similar plans) should be generated out of the
issue-tracking-system (Bugzilla).
Bugzilla Plan generation would be an task for the suggested project:
[PROJECT] - Collaboration and Government Infrastructure (CAGI)
http://www.eclipse.org/newsportal/article.php?id=20&grou p=eclipse.foundation
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.
..
--
http://lazaridis.com
|
|
|
|
Powered by
FUDForum. Page generated in 0.97411 seconds
] 
Search
Help
Register
Login
Home
