OpenJDK bug database: Status update
joe.darcy at oracle.com
Wed Mar 21 20:43:31 PDT 2012
Just a quick follow-up, our overriding priority for the next few months
is to make sure some bug system is continuously available for the JDK.
With that goal, it possible that both some Oracle-internal as well as
external boundary systems, like bugs.sun.com, are not ready to be
migrated over when the cutover to the internal JIRA instance occurs.
If that happens, there may some temporary gaps in the availability of or
stale data in the boundary systems. However, as Roger indicates, our
goal is to provide analogous access to JDK bug information from internal
JIRA as is done today from the legacy bug system, subject to making the
core migration deadlines.
during the internal JIRA phase (before the external JIRA phase) our
intention is to provide
On 03/21/2012 10:26 AM, Roger Calnan wrote:
> no the goal is to continue the external access to the bugs
> pulling the data from the internal JIRA rather than the old system,
>> Does this mean there will be a period where access to bug details
>> is only available internally at Oracle and an external user can't,
>> for instance, look up the details of a bug corresponding to an ID
>> in the Mercurial repositories?
>> Andrew :)
>> Free Java Software Engineer
>> Red Hat, Inc. (http://www.redhat.com)
>> PGP Key: 248BDC07 (https://keys.indymedia.org/)
>> Fingerprint = EC5A 1F5E C0AD 1D15 8F1F 8F91 3B96 A578 248B DC07
More information about the discuss