Any update for the bug database?

[David Herron]

Oh yeah Tom, you just reminded me of another question...

The OpenJDK incorporates code from some external projects.  Just like 
many projects do.

So it wouldn't be just how do we push bug data between the public and 
private systems; but how do we interface our bugs with our own upstream 
projects?  What happens when a bug in one project becomes dependant on a 
bug in some other project? 

I suppose that today the connection is handled manually.. e.g. set a URL 
in the bug description or evaluation.  Wouldn't it be nice if the bug 
systems automatically handled these connections?  Some kinda protocol 
between bug systems.  But this is much to large a problem to consider 
fixing on a global scale right away.

As for targeting a bug for multiple releases ...  clearly a bug can 
appear in multiple releases depending on when the bug was created and 
when it was found.   We tend to fix an issue in the HEAD release and 
optionally backport it to earlier releases based on customer needs.  For 
example this lets the fix bake in the HEAD release to give some time for 
testing and usage to shake out whether any bugs were created in the 
process of fixing the bug.  (I don't care how good a developer you are; 
sometimes more problems are created while trying to solve a problem)   
This means the bug status (closed/fixed/open/etc) needs to be maintained 
for each related release.

- David Herron


Tom Tromey wrote:
>>>>>> "David" == David Herron <David.Herron at Sun.COM> writes:
>>>>>>             
>
> David> It will be best if there is one pile of bugs to deal with.
> David> That leaves the question, how do we handle openjdk bugs from
> David> the community AND handle bugs coming from all the existing
> David> channels we already have?  We have bug fields containing
> David> confidential customer information we cannot expose, we have
> David> security bugs we don't expose due to our policies of handling
> David> security bugs, etc.
>
> One stock solution followed by other projects is to have two bug
> systems -- one for the open source project and another for the
> company.  Then you just need ways, perhaps just manual ones, of
> pushing bugs "upstream" from the Sun tracker to the OpenJDK tracker.
>
> There are exceptions to this, though -- e.g., bugzilla.redhat.com is
> used for both Fedora and all kinds of Red Hat things.  Personally I
> don't think this is the best way to go.
>
> Anyway, is this discussion being held in public?  That would be
> worthwhile.
>
> David> A key flaw with bugzilla is it can target only one release.
>
> Yeah, this is reasonably painful.
> There are folks writing "distributed VC-like" bug tracking systems but
> AFAIK none has really caught on yet.  The basic idea here, AIUI, is to
> have the bugs in the tree, so they can be closed, managed, merged,
> right along with the sources.
>
> Tom
>   

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openjdk.java.net/pipermail/discuss/attachments/20070521/ea5e07e7/attachment.html>