Comments in-line...
On Mar 6, 2006, at 11:58 AM, Henri Yandell wrote:
On 3/2/06, David M Johnson <[EMAIL PROTECTED]> wrote:
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
Only issue is the last one - tends not to be the way OSS projects do
the process of their issues - but I'm not against it. Provided we're
not giving people the ability to close other people's issues
I like the idea of allowing the person who reported the bug to close
the bug if they can verify that it is indeed fixed, but clearly
that's not going to fly here.
"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?
Yes :)
People should be able to close their own bugs, but not other peoples -
not sure if Jira allows that. If we had testers who we trusted to be
managing our issues - why wouldn't they be committers?
Yes. Now we just have to figure out how to get our testers to
participate here on the list, contribute test plans, test reports,
etc. so that they can become committers some day.
-Dave
