OpenJDK bug database: DRAFT Developer Workflow

[Alan Bateman]

On 01/01/2012 03:44, David Holmes wrote:
>
> I think that is actually a good example of a bad situation. If I want 
> bugs fixed in a given release or build I don't want to have to select 
> all Closed bugs and then weed through them based on substates - as per 
> your "good JIRA rule". I'd advocate two different final states (as 
> opposed to our current system) that distinguishes between "closed and 
> something was changed" versus "closed and nothing happened".
I think there is merit in this suggestion. With the current draft then 
this query would have to match bugs that are in the Fixed state plus 
bugs that are in the Closed state for reasons Verified, Unverified, or 
Fix Failed. I periodically need to hack up SQL queries to the current 
bug database and dealing with the closed substates is a pain. However, 
this is nothing compared to the complexity of crafting queries that work 
with multiple releases. Multiple releases is TBD in the current draft 
but once that is fleshed out then I think canned queries will become 
more critical.

-Alan