JDK bug migration moves to JIRA, public system almost here
Stage one of Oracles huge migration of bug systems has been completed – a fully public bug tracker isnt far away.
Oracle’s lengthy battle to migrate the OpenJDK bug
database has reached an important milestone, with the
legacy Sun “bugtraq” system now housed in an internal JIRA
The original plan to shift Sun’s “creaky old legacy system” to a OpenJDK JIRA was outlined almost a year ago by Chief Architect of the Java Platform Mark Reinhold. However, it became apparent in March that the task of moving bug infrastructures in one fell swoop was too much for the OpenJDK team of contributors to handle, hence this internal step first.
As Joseph D. Darcy details on the Oracle blog, around 140,000 distinct issues have been imported to the JIRA instance, showing the scale of the task at hand - and that’s without even considering the difference in the schemas. Separately, the Code Tools OpenJDK project has had its own JIRA project populated with several thousand existing bugs.
Darcy also notes the five different states for the OpenJDK JIRA projects, in an attempt to simplify the system, which are as follows:
- In progress
Whilst onlookers won’t be able to see a visible difference from the legacy system just yet, one big noticeable change is the numbering system: the JIRA JDK project will file new issues from 8,000,000, although the reason for this is unspecified
Now the internal shift has occurred, the next stage for Oracle’s bug tracker is to go public. Although the date for externalisation isn’t set in stone (it won’t be JavaOne, says Darcy), it should be noted just how far this effort has come. It’s a mammoth task transferring across bug infrastructures and it’s great to see that Oracle is still firmly committed to a public bug system for the entire Java community to track.