OpenJDK bug database: DRAFT Developer Workflow

[David Holmes]

On 16/12/2011 3:27 AM, Kelly O'Hair wrote:
>
> On Dec 14, 2011, at 11:13 PM, David Holmes wrote:
>
>>>
>>> The source for the information you really want about whether a fix
>>> has been
>>> applied should come from the source control system, not the bug system.
>>> That's the only information you can really trust.
>>
>> I'm not aware of any way to run queries against mercurial the way we
>> can with BQ and will be able to with Jira. I echo Joe's sentiment that
>> having both resolved and unresolved issues be "closed" makes it harder
>> to find those resolved issues. Doing bug triage is aided immensely if
>> you can query which bugs were fixed in a specific build of a specific
>> release.
>
>
> This page is generated from the Mercurial repositories:
> http://download.java.net/jdk7u4/changes/jdk7u4-b03.html
> The script, or a variation of it for openjdk6, is at
> http://hg.openjdk.java.net/jdk6/jdk6/file/tip/make/scripts/jdkreport.pl
>
> So I do think it is possible to query the repositories for what bugs
> were fixed.

Okay - yes you can post-process "hg log" output, but unless there is a 
nice GUI front-end for this I don't think it is viable as a replacement 
for the reporting functionality provided by BQ or JIRA. So to return to 
the original point I still think that the bug workflow should aid such 
queries by distinguishing between closed-resolved and closed-not-resolved.

There's no reason for the bug database to lag the repository metadata if 
we can add the right hooks so that pushes update the bug report.

Cheers,
David

>
> -kto
>