Author Topic: Q&T Members - The Bug Fixing Process  (Read 11504 times)

aravot

  • Peter
  • Moderator
  • Sr. Member
  • *
  • Posts: 2874
    • VirtueMart Extensions
Q&T Members - The Bug Fixing Process
« on: September 11, 2007, 09:44:24 am »
The Forum:

1. A bug is reported on the Q&T Forums.
2. A Q&T Working group member will review the bug and attempt to confirm the report.
3. If the bug can be confirmed, test the report on the latest SVN checkout to make sure it hasn't been fixed already.
4. If the bug has been fixed in SVN, tag it as [FIXED IN SVN:####] where #### is the SVN revision that you tested against.
5. If the bug has been fixed in SVN and has been tagged as fixed, move it to the Q&T Resolved forum and you are done.

6. If the bug could NOT be confirmed, reply to the thread that you could not confirm the bug and request more information from the bug reporter. Mark the thread as [UNCONFIRMED].  Wait for feedback from the bug reporter and then start over at step 2.

7. If the bug can be confirmed and is not fixed, reply to the report that you were able to confirm the report. Once you have replied that you could confirm the report, create a tracker artifact for the bug. Fill in all the information that you can from the bug report; set the tracker artifact status to Confirmed and assign it a priority based on the priority guidelines. Make sure you put a note in the tracker artifact that this artifact was created based on a forum report and insert a link back to the forum thread for quick cross referencing.

8. Once a tracker artifact has been created, reply to the thread that a tracker artifact has been created and post a link to the tracker artifact. Tag the thread as being on the tracker with [TRACKER:####] where #### is the tracker artifact number from now on only the tracker item gets updated.

9. Now it is up to a developer to fix the bug. We are off the hook until they have committed a fix for the issue.
10. Once a fix has been committed, the developer should mark the tracker artifact as "Pending".
11. Test the fix that has been committed, if the problem is resolved, mark the artifact as "Fixed in SVN".  The report has been resolved move the post to the Resolved Forum.

12. If the fix could not be confirmed, reply to the artifact on the tracker what problems still exist and steps to duplicate the problems and then change the artifacts status to "Incomplete".
13. Repeat step 9.


The Tracker:

1. A bug is reported on the tracker.
2. A Q&T Working group member will review the bug report and attempt to confirm the report.
3. If the bug can be confirmed, test the report on the latest SVN checkout to make sure it hasn't been fixed already.
4. If the bug has been fixed in SVN, change the artifact status to "Fixed in SVN" and post a comment that it is already fixed in SVN. You are done.

5. If the bug report could NOT be confirmed, reply to the artifact saying that you were unable to confirm the report and request more information. Update the artifact status to "Unconfirmed". Wait for feedback from the bug reporter and then start over at step 2.

6. If the bug can be confirmed and is not fixed, reply to the artifact that you were able to confirm the report. Once you have replied that you could confirm the report, change the status to "Confirmed" and assign it a priority based on the priority guidelines.

7. Now it is up to a developer to fix the bug. We are off the hook until they have committed a fix for the issue.
8. Once a fix has been committed, the developer should mark the tracker artifact as "Pending".
9. Test the fix that has been committed, if the problem is resolved, mark the artifact as "Fixed in SVN".  The bug report has been resolved.

10. If the fix could not be confirmed, reply to the artifact on the tracker with the problems that still exist and steps to duplicate the problems and then change the artifacts status back to "Open".
11. Repeat step 7.


Priority Guidelines
Quote
1 – High - Something is really broken it should be taken care of pronto.
2 – Medium - This is not a full breakage but it doesn't work like it is supposed to or not all the time.
3 – Low - This is just an annoyance, something is not quite right, but basic functionality is still present.