Difference between revisions of "BugSquad/Triage Guide"
| Line 31: | Line 31: | ||
=== Ask someone to verify your changes === | === Ask someone to verify your changes === | ||
| − | For the first bugs we encourage you to | + | For the first bugs we encourage you to make the changes in conjunction with a member of the bugsqad team. You will find them at #sugar on freenode. |
=== Make your changes === | === Make your changes === | ||
Revision as of 05:11, 25 September 2008
Bugsquad Triage Guide
Why bug triaging is helpful?
- filter out duplications
- verify that the information, needed by the developer to fix the bug, is present
- verify that the bug is filed against the correct component
- verify that the bug has the correct software version field
Maintainers duty
- find out the priority of the bug
- assign bug to a specific milestone
How to get up to speed
Create a trac account
Create a trac account at laptop.org.
Join the sugar mailing list
To keep up to date with the recent discussion and developments we recommend joining the sugar mailing list. We might create a separate list for the Bugsquad in the future.
Read the Stock Responses
The BugSquad/TriageGuide/StockResponses are general examples of the kinds of comments that triagers should add to bug reports. Please read them carefully. In most cases you can use one of them as a comment.
Triaging
Pick a bug
Use the tracker to create a query http://dev.laptop.org/query. This for example creates a query for all open sugar bugs. Choose one you want to triage and read it carefully.
Find what should be changed
Read the Steps of Triaging to determine what should be changed (if anything) and how.
Ask someone to verify your changes
For the first bugs we encourage you to make the changes in conjunction with a member of the bugsqad team. You will find them at #sugar on freenode.
Make your changes
After someone verifies your changes (and likely refines them and/or points out other changes), either make those changes yourself or make sure that the reviewer makes them.