OpenJDK bug database: DRAFT Developer Workflow
volker.simonis at gmail.com
Wed Dec 14 00:39:30 PST 2011
nice to hear that somebody is working on this.
I have some questions around end user / external user access to the new system:
1. Who will be able to open a new bug/RFE?
b. registered users only (with some trivial click-trough registration)
c. only special roles as defined in the OpenJDK bylaws (i.e.
Participants, Contributors, Authors, Committers, Members..)
I would strongly vote for variant a. or b. but if you choose variant
c. at least every "Participant" (i.e. everybody who subscribed to an
OpenJDK mailing list) should be able to open new bugs/RFEs.
2. Who will be able to change bugs/RFEs?
This is somewhat related to question 1. Of course I understand that
this will have to be handled more restrictive, but at least commenting
on a bug should be handled as liberal as possible (i.e. at least as
liberal as in the answer for 1).
3. Will it be possible to "subscribe" to a bug/RFE in order to get
notified of any changes?
Again a crucial feature for me which should be handled as liberal as
possible. The author of a bug should be placed automatically on the
subscription list (which would of course require some kind of
registration - e.g. with the credentials of a "Participants")
4. Will newly entered bugs/RFEs be immediately visible with a valid,
immutable Bug ID (i.e. will they have status "Dispatched")
- As you probably all know, currently new bugs filed from outside
Oracle only get a temporary Bug ID until they are evaluated and
promoted by somebody inside Oracle (which can take weeks..). I think
this is simply a "no-go" for a real open source project.
- Even bugs filed by Oracle employees need a day or more until they
become publicly visible. Will this improve with the new system?
Regards and please keep on pushing this,
On Tue, Dec 13, 2011 at 8:39 PM, Iris Clark <iris.clark at oracle.com> wrote:
> I'm defining requirements for the OpenJDK bug database . 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.
> 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.
>  http://mail.openjdk.java.net/pipermail/announce/2011-October/000112.html
More information about the discuss