OpenJDK bug database: DRAFT Developer Workflow
iris.clark at oracle.com
Mon Dec 19 08:51:56 PST 2011
I'm thrilled to hear that you're thinking of ways for us to engage more
of the community!
My initial thought was to have a customized workflow for end-user bugs
that could take into account the typical interactions that occur for that
triage. I don't expect it to be complex, but I could be wrong. I haven't
figured out how to define the set of users who can do the triage.
OpenJDK Authors doesn't sound quite right, but that's along the right
lines, a little bit more commitment than being a Participant and
self-nominating with low requirements threshold.
I was hoping to get a chance to find out details of how end-user bugs are
handled internally before the holidays, but I'm not confident that will
happen. (I'll be out beginning on Wed, back the first few days of Jan.)
From: Martijn Verburg [mailto:martijnverburg at gmail.com]
Sent: Monday, December 19, 2011 8:27 AM
To: Iris Clark
Cc: Alan Bateman; discuss at openjdk.java.net
Subject: Re: OpenJDK bug database: DRAFT Developer Workflow
> In my mind, this would be ideal.
I'm planning on having a good community structure in place (it's already forming via the Adopt a JSR, and OpenJDK adoption programs) by the time this JIRA move occurs (mid 2012 I'm guessing?). So perhaps if the initial JIRA workflow design takes this into account? Perhaps an alternative workflow can be thought of in case that initiative fails for whatever reason (but hopefully once a deep roots community forms around this that won't be a problem).
> -----Original Message-----
> From: Martijn Verburg [mailto:martijnverburg at gmail.com]
> Sent: Monday, December 19, 2011 5:39 AM
> To: Alan Bateman
> Cc: discuss at openjdk.java.net
> Subject: Re: OpenJDK bug database: DRAFT Developer Workflow
> Hi Alan/All,
>>> Just on this, what are the real numbers we are talking about here?
>> I remember Roger Lewis provided some data on this. I found one mail
>>  where he said 450/month. There is clearly potential to
>> crowdsource these incidents but would need some way to move real bug
>> reports to the right place.
> OK, it's not as bad as I feared, but nor is it a number that can just be left unmanaged. I think this is a case where the wider OpenJDK community and the JUG membership could act as a crowd sourced triage. This would hopefully let the OpenJDK comitters focus on the confirmed issues.
More information about the discuss