Monday Nov 17, 2008

OpenJDK and bugs.sun.com

Yeah yeah, I haven't done a blog in a while.

For the most part I work on build related bugs in most of the JDK releases, so I thought it might be helpful for people to see what kind of build bugs we are talking about. Granted this is via bugs.sun.com and is a bit of a "one way street" for the open source community, but the content is still valid. Once we have a true open source bugzilla instance working for OpenJDK, the mechanism changes (becoming more open of course).

In the current bug tracking system you see via bugs.sun.com we are using has a category ("java" in my examples) a subcategory ("build" in my example), and I'm using the bugStatus selection which is a number between 1 and 11.

So here are the JDK Build Change Requests (CRs) (CRs cover both bugs and rfes) for all releases, listed based on the state of the bug:

  1. Dispatched (Submitted but not officially accepted yet)
  2. Incomplete (Some kind of missing information)
  3. Accepted (Someone has at least taken a quick look at it)
  4. Defer (No work being done on it for some reason, rare state to be in)
  5. Cause Known (Generally it's understood what the cause is)
  6. Fix Understood (The necessary fix is understood)
  7. Fix in Progress (The fix is in progress)
  8. Fix Available (The fix has been implemented somewhere, access may be limited)
  9. Fix Failed (The fix does not work, rare state, usually goes back to Fix In Progress)
  10. Fix Delivered (The fix has been pushed into an official repository forest, official is public for OpenJDK)
  11. Closed (All activity on this CR has stopped, could be a verified fix, could be closed as not a bug)

The general rules about the bug states have a little flexibility between teams and products, but the above is pretty close for most of them. It's normal that when a bug is Accepted, that it gets an engineer assigned to it, but that is not a hard and fast rule. Also, many bugs reach the "Fix Delivered" state and remain there forever, never being changes to "Closed" as a verified bug, not exactly sure why that happens.

-kto

About

Various blogs on JDK development procedures, including building, build infrastructure, testing, and source maintenance.

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