OpenJDK bug database: DRAFT Developer Workflow

[Georges Saab]

Please see inline

On 16 dec 2011, at 14:45, Iris Clark wrote:

[snip]
> 
> From: John Pampuch 
> Sent: Friday, December 16, 2011 2:20 PM
> To: discuss at openjdk.java.net
> Subject: Re: OpenJDK bug database: DRAFT Developer Workflow
> 
> 
> 
> Iris-
> 
> One concern I have in the "Accepted" state that you describe below is that it may set expectations with someone who is paying attention to the bug.  On many bugs, the target release can't really be determined until we understand the bug better.  If we could, I'd prefer requiring setting the target release until step 4.
> 
> -John
> 
[snip]


Two comments on this:

1. I personally like the terms 'unconfirmed' and 'confirmed' rather than 'accepted' in part to be clearer about expectations.
2. IMHO targeting should not be viewed as a commitment TO FIX in a specific release, rather a commitment TO WORK on 
the bug in the context of the release.  For instance, a bug which appears to be very important if it really exists might be 
immediately targeted to the current update release, meaning -- we need to work on this in the context of this release
until we know that it is not a bug or not as important a bug as it sounds now, in which case it could be retargeted to a
later release.