Comment 1 for bug 163694
Revision history for this message
| Chris Gregan (cgregan) wrote Re: Fix Committed/Released distinction is inconsistent and unproductive | #1 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
This is currently a discussion in QA/Mobile QA about the need to confirmation of fixed issues and how there is currently no means of tracking the fact that a fixed issue has been confirmed by testing.
My initial reaction was to use "Fix Committed" as a catch all for development, so when development pushed the code to the release repo, the status would change to Fix Committed.
Once the fix is in this Committed state, QA would know that the code is available and could then download. If the fix was then verified to be fixed then the bug state would move to "Fix Released" so the greater community would know that they could now be assured that the fix was there.
The current fix verification system relies on tags which cannot be tracked or used as the basis for performance matrices. A move to this process would free Dev from having to worry about two status settings, and give QA a way of showing a bug fix was tested and proven.