OpenJDK bug database: DRAFT Developer Workflow
martijnverburg at gmail.com
Mon Dec 19 08:26:49 PST 2011
> 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