Final Call for Comments - RE: OpenJDK bug database: DRAFT Developer Workflow

[Iris Clark]

Hi, John.

Nothing heavy weight.  There aren't meetings and no voting other than by individuals putting forth convincing arguments on this list.  I'll be reviewing all of the comments which have been received and providing comments or requesting clarification as necessary.  In cases where there is significant consensus on a solution which allows for a reasonable implementation, that will be path.  In cases where there are fundamental differences in opinion, I'll make a decision.

iris

-----Original Message-----
From: John Pampuch 
Sent: Thursday, January 05, 2012 5:37 PM
To: discuss at openjdk.java.net
Subject: Re: Final Call for Comments - RE: OpenJDK bug database: DRAFT Developer Workflow

Do you have a process for reconciling the differences that have been expressed?

-John

On 1/5/12 5:06 PM, Iris Clark wrote:
> Hi!
>
> I am very pleased to see that there is public discussion about the Developer workflow.  It is my expectation that there are many opinions about what the optimal system should be and I'm happy to see that people are comfortable expressing those opinions.  I never expected consensus.  I think it is beneficial for everybody who will use the system to see what kinds of concerns people have.
>
> Now that I'm back from vacation, I'd like to start wrapping up the feedback period for the Developer Workflow for the Pilot.  I'll be working on balancing everybody's concerns between now and the next version of the Developer Workflow.  Please keep in mind that that changes will be possible during the Pilot.
>
> I strongly encourage you to get your final comments within the next week (12:01AM Sat, 14 Jan PT) so that all of our major options/concerns are on the table.
>
> Thanks,
> iris
>
> -----Original Message-----
> From: Iris Clark
> Sent: Tuesday, December 13, 2011 11:39 AM
> To: discuss at openjdk.java.net
> Cc: Iris Clark
> Subject: OpenJDK bug database: DRAFT Developer Workflow
>
> Hi!
>
> I'm defining requirements for the OpenJDK bug database [1].  As one would guess, it's not easy.  We have more than 15 years of data, process evolution, and supporting tools that we need to consider.
> Opinions on the effectiveness of existing process and tools vary.
> Many people with different roles (end-users, developers, quality, release management, etc.) need to be able to access the system.
>
> I've written a preliminary draft of what the pilot workflow for bugs and RFEs might look like.  It is based on the existing bug system with modifications to omit portions that aren't used.  There is no requirement that we stick closely to this draft, though any changes will need to consider the impact on data migration.  It still needs quite a bit of work.
>
>    http://cr.openjdk.java.net/~iris/jira/JIRAforOpenJDK.html
>
> Please send feedback/comments to this mailing list.  I'll provide regular updates as feedback is incorporated and I fill in other sections of the document.
>
> Thanks,
> iris
>
> [1] 
> http://mail.openjdk.java.net/pipermail/announce/2011-October/000112.ht
> ml