By kto on May 11, 2008
Until the OpenJDK project converts to Bugzilla, I thought some more information about how our internal bug tracking system works might help people watching the current situation.
The OpenJDK change requests (CRs) or bugs are currently visible at bugs.sun.com.
There are 11 states for a CR and the normal change of state is the following:
- Dispatched: The initial state for a new CR.
- Incomplete: Something critical is missing from the CR.
- Accepted: CR was accepted, the first step in being investigated and fixed.
- Defer: Work on this CR is on hold.
- Cause Known: A basic understanding of the problem is known.
- Fix Understood: A basic fix is now understood.
- Fix in Progress: The assigned engineer is actively working on the fix or getting it integrated.
- Fix Available: A changeset or the actual fix has been made available in a team area.
- Fix Failed: Something went wrong with the fix.
- Fix Delivered: The changeset or fix has been integrated into the master area and will show up in the next build promotion.
- Closed: There are many reasons why a bug will be in the closed state. It might be verified as fixed, closed as a duplicate, closed as 'not a bug' or closed as 'will not fix'.
The states 1-9 are considered "unresolved", so until a bug becomes "10 - Fix Delivered" or "11 - Closed", it is still considered unresolved. So being "unresolved" may mean that a fix is available, just not in a position to be made part of a formal build promotion.
The bugs.sun.com interface is read-only and somewhat crude, but you can query the bug information, for example the Unresolved JDK Build Subcategory Bugs and RFEs. Hope this helps explain things.