OpenJDK bug database: DRAFT Developer Workflow
georges.saab at oracle.com
Thu Dec 15 17:01:03 PST 2011
Hi Volker --
Please see inline...
On 15 dec 2011, at 05:45, Volker Simonis wrote:
> Hi Iris,
> I personally don't think that two parallel JIRA instances will be
> particularly useful. They will be just a constant cause of confusion.
> Because eventually you'd have to transfer bugs from the "end-user" bug
> system to the "real" bug system. And even if you'd somehow manage to
> keep the bug ids unique between the two systems, you would still have
> two systems with all the drawbacks:
> - which system to search (before entering a new bug)
> - in which system to track the bug
> - you'll have to keep the bug content in sync between the two systems
> (otherwise, if you just move the bug from one system to the other,
> links to the original bug won't be valid any more)
> So please stick to one system if possible. You could for example just
> introduce a new state "UserBug" in the workflow which comes just
> before "Dispatched".
Currently there is a system (web-bugs) for handling bug reports from end users.
Most of these are not developers. Most have no idea what information is needed
to track down an issue. There are millions of these reports that come in
each year. Many need more info. Many are duplicates. Many are not even bugs.
Every once in a while something really really important comes through this
IMHO - we want end users to be able to file reports, but keep them separate
from the database used by development. We want the OpenJDK community to
be able to help triage and respond so that it is possible to scale the way we deal
with these and not miss real and important reports -- but get these swiftly and
smoothly transitioned to the development JIRA project.
More information about the discuss