Linda Skrocki, our program manager at Sun has been helping out by
reviewing the bugs in JIRA, looking for duplicates and work that's
already been completed. She is in the process of CLOSING a lot of
bugs that I marked RESOLVED. I have always used RESOLVED to indicate
that a bug is fixed and I'm done working on it. So think of this as a
"cleanup the database before it's transfered to Apache" measure.
It might be time to have a discussion about how those bug states
figure into our release process, so we know what to do moving
forward. Here are the workflow steps in JIRA and how they might be
interpreted:
Open - when an issue has arrived
In progress - when a developer started working on an issue
Resolved - when a developer claims a bug is fixed
Reopened - when a resolved issue turns out not to have been resolved
Closed - when a tester or end-user verifies that bug is fixed
"Closed" is a tricky one. Who can close a bug? Must that be a
committer? What if none of our testers are committers? Must a
committer verify each bug before it is closed?
- Dave
