Update on bug system for OpenJDK (web-discuss)

Andrew Haley aph at redhat.com
Thu Jun 2 13:35:38 UTC 2011

On 06/02/2011 01:05 PM, Geir Magnusson Jr. wrote:
> On Jun 2, 2011, at 4:57 AM, Andrew Haley wrote:
>> On 01/06/11 19:40, Geir Magnusson Jr. wrote:
>>> On Jun 1, 2011, at 12:28 PM, Andrew Haley wrote:
>>>> On 06/01/2011 05:03 PM, Dalibor Topic wrote:
>>>>> On 6/1/11 4:43 PM, Andrew Haley wrote:
>>>>>> On 06/01/2011 03:28 PM, Dalibor Topic wrote:
>>>>>>> On 5/31/11 3:23 PM, Andrew Haley wrote:
>>>>>>>> If you funnel all bug reports through an internal closed group, you
>>>>>>>> will have a scaling problem, and there will be a bottleneck between
>>>>>>>> bug reporters and bug fixers.
>>>>>>> Thanks for the good explanation. My next question would be wherefrom 
>>>>>>> to source such a crowd that scales?
>>>>>> The set of OpenJDK contributors would be a start.
>>>>> That's a good idea, but the thread so far wasn't very conclusive on 
>>>>> contributors embracing such a task, unless I have misread it.
>>>>> Note that I'm not saying it's not worth doing, but I'd like to read 
>>>>> something more than 'build it and they'll come' to understand why a 
>>>>> crowd sourced from contributors would scale at that task. 
>>>> Surely it's better than only the Oracle team.  How could it be worse?
>>> Aren't the contributors "the team" anyway?
>> I don't know.  This is the first time that anyone has used "the team"
>> without qualification.  What's the relevance of this?
> Really?  Relevance?  I guess I was just baffled at why the full set
> of contributors to OpenJDK wouldn't be considered "a crowd" or "the
> team" or whatever term you want to use for the purpose of bug triage
> and management.

I think you must have missed the earlier part of this discussion.  The
question is whether bug triage should be done by an Oracle-only team,
as proposed, or by a wider group of contributors, as suggested by me.


More information about the discuss mailing list