Update on bug system for OpenJDK (web-discuss)

Roger Calnan roger.calnan at oracle.com
Fri Jun 3 07:23:31 UTC 2011

	perfect, looks like that we have solved that mystery!...  hopefully
it is now clear that triage of developer bugs is going to continue as today, 
in the open.


	something that has come out of this thread that needs to be thought 
through is we need some flexibility in how we manage/triage the bugs that
are submitted by the users of JavaSE (vs. the developers) may need to
vary depending on the platform/component the bugs are reported on.


	another element of "support" that needs to be part of the mix is
that we (Oracle) don't just handle questions from developers who use
the JRE, but also their end customers.  We get *lots* of feedback from
consumers/end-users off:


the intention is to continue this support.  How we do this has not yet
been determined  we will likely use the bug system that we choose
for developer bugs as the DB for these issues we use now is very old.
These reports however will remain private as the consumers who report
issues do so with no intention of their reports being public and the level
of detail one gets if very low, so one has to filter looking for patterns
rather than reading every item.  Some issues will end up as bugs in the
main system and will need to be fixed in the JRE.



> 2011/6/2 8:56 -0700, kelly.ohair at oracle.com:
>> On Jun 2, 2011, at 8:13 AM, Roger Calnan wrote:
>>> Andrew Haley wrote:
>>>> The question is whether bug triage should be done by an Oracle-only team,
>>>> as proposed, 
>>> who proposed this?
>> Yeah, who proposed this? I'm pretty sure we do NOT want an Oracle-only
>> team doing triage.
> I mentioned this as an assumption, not a proposal, but you can blame me.
> I've since been talked out of it.
>> One of the primary reasons for a completely open bug system is to get
>> away from any contribution sponsoring by Oracle employees, an obvious
>> bottleneck.
> Completely agree.
> - Mark

More information about the discuss mailing list