JDK bug migration: bugs.sun.com now backed by JIRA

The JDK bug migration from a Sun legacy system to JIRA has reached another planned milestone: the data displayed on bugs.sun.com is now backed by JIRA rather than by the legacy system. Besides maintaining the URLs to old bugs, bugs filed since the migration to JIRA are now visible too.

The basic information presented about a bug is the same as before, but reformatted and using JIRA terminology:

  • Instead of a "category", a bug now has a "component / subcomponent" classification. As outlined previously, part of the migration effort was reclassifying bugs according to a new classification scheme; I'll write more about the new scheme in a subsequent blog post.

  • Instead of a list of JDK versions a bug is "reported against," there is a list of "affected versions." The names of the JDK versions have largely been regularized; code names like "tiger" and "mantis" have been replaced by the release numbers like "5.0" and "1.4.2".

  • Instead of "release fixed," there are now "Fixed Versions."

  • The legacy system had many fields that could hold a sequence of text entries, including "Description," "Workaround", and "Evaluation." JIRA instead only has two analogous fields labeled as "Description" and a unified stream of "Comments."

Nearly coincident with switching to JIRA, we also enabled an agent which automatically updates a JIRA issue in response to pushes into JDK-related Hg repositories. These comments include the changeset URL, the user making the push, and a time stamp. These comments are first added when a fix is pushed to a team integration repository and then added again when the fix is pushed into the master repository for a release.

We're still in early days of production usage of JIRA for JDK bug tracking, but the transition to production went smoothly and over 1,000 new issues have already been filed. Many other facets of the migration are still in the works, including hosting new incidents filed at bugs.sun.com in a tailored incidents project in JIRA.

Comments:

Hi,
I noticed that my old bug links return HTTP Status 404. Examples:

No longer works (note no "bugdatabase/" in URL):
http://bugs.sun.com/view_bug.do?bug_id=6440214

OK:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6440214

Is this caused by the migration?
Thanks

Posted by Konrad on October 25, 2012 at 06:37 PM PDT #

@Konrad,

We are aware that the shorter form of the old links without "bugdatabase" give a 404 currently and we're looking into a fix.

Posted by Joe Darcy on October 25, 2012 at 06:44 PM PDT #

Does this mean the votes are gone now?

Do we have to re-vote?

Or are votes meaningless now anyway?

Posted by guest on October 26, 2012 at 10:03 AM PDT #

@Would-be-voter,

We are still working out how general comments and if / how voting will operate with the migration to JIRA.

Posted by Joe Darcy on October 26, 2012 at 12:21 PM PDT #

Hello, I'm glad to know that the old bug database has been migrated to JIRA and that progress is still ongoing (I also noticed the problem of the old links without "bugdatabase" not working).

However, I have another question: is there a way to access this JIRA istance directly, without using the old "bugs.sun.com" interface?
In fact, with the old interface:
- searching features are limited
- you can't comment/vote
- I've lost my "watches" on bugs I'm interested in

So, it's essential that the old bugs have been migrated to the new system, but from now on I would appreciate to use the full power of JIRA if possible.
I was not able to find any link to this new JIRA instance anywhere! :-(

Thanks in advance,
Mauro

Posted by Mauro Molinari on October 31, 2012 at 01:33 AM PDT #

@Mauro,

The JIRA instance cannot currently be accessed directly outside of Oracle. We're calling the process to make it available on the wider internet "externalization."

We don't have published timeline for that to finish, but we are working on it!

Posted by guest on October 31, 2012 at 09:10 AM PDT #

It goes without saying (but this is Oracle so I'll say it just in case) that the ability to comment, watch and vote on issues is *extremely* important to users.

Gone are the days where companies can push out announcements and expect users to consume it quietly. We need the ability to respond. We need the ability to provide feedback. There have been numerous cases in the past where bugs were closed as fixed even though they were not actually fixed.

Why should this bug system work any differently than Netbeans? They have a public system where users can even reopen closed bugs if they feel the problem was not resolved, and yet the sky does not fall. Oracle should consider doing the same.

Posted by Gili on November 01, 2012 at 04:42 PM PDT #

Apache River is the continued developement of Sun's Jini project, up until recently Jini bugs were listed in the Sun bug database, now unfortunately we no longer have access. We'd be very appreciative if Oracle was able to donate a text file dump of Jini bugs.

As a side note, we've solved bugs that remain in RMI and distributed garbage collection and we have a concurrent policy based on immutability that'll blow the doors off the standard sun PolicyFile implementation.

Regards,

Peter.

Posted by peter on November 05, 2012 at 03:15 AM PST #

@Gil,

We are working to restore the archived comments and votes on bugs.sun.com and to allow new comments and votes to the filed.

Posted by Joe Darcy on November 05, 2012 at 11:05 AM PST #

Hi Joe,

Thanks for the response. Will users and Oracle engineers have the ability to "watch" bug reports and/or comments? It would be great to post comments against a bug, have the Oracle engineer receive a notification, and in turn notify the user when he/she replies.

This is all standard JIRA stuff. I'm just wondering if you're going to allow its use.

Posted by Gili on November 05, 2012 at 11:08 AM PST #

@Gil,

People who have full accounts on the system will certainly be able to access those JIRA features. The exact set of account privileges for those who don't have any designated OpenJDK role (author, contributor, reviewer, etc.) is part of the details of the externalization process that haven't been worked out yet.

Posted by Joe Darcy on November 05, 2012 at 11:25 AM PST #

I am waiting for the new bug report system to be up and running to report some bugs, on OpenJDK. I'm using a zipped version called "java-se-7-ri" which is extremely useful for testing rather than the install version.

Posted by guest on November 17, 2012 at 08:03 AM PST #

@java-se-7-ri user,

It sounds like you are using the reference implementation (RI) of Java SE 7 which was included as part of the JSR 336 materials. Note that this version is fixed in time and has a special status with regards to conformance testing of Java SE 7. Unless special circumstances hold, other implementations of Java SE 7, such as the current JDK 7 update release, should be used instead since they have had security fixes applied, etc.

Posted by Joe Darcy on November 26, 2012 at 09:42 AM PST #

Post a Comment:
Comments are closed for this entry.
About

darcy

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today
News

No bookmarks in folder

Blogroll