3,267
edits
Homepage | Activities | Events | Lists | Development | Translate | Contact
Changes
Jump to navigation
Jump to search
Line 24:
Line 24: − + + + + + + + + + +
BugSquad/Triage Guide (view source)
Revision as of 05:09, 25 September 2008
, 05:09, 25 September 2008→How to get up to speed
=== Pick a bug ===
=== Pick a bug ===
Use the tracker to create a query http://dev.laptop.org/query. This for example creates a query for [http://dev.laptop.org/query?status=assigned&status=new&status=reopened&component=sugar&order=priority&col=id&col=summary&col=status&col=owner&col=type&col=milestone all open sugar bugs]. Choose one you want to triage. For the first bugs we encourage you to do it in conjunction with a member of the bugsqad team. You will find them at #sugar on freenode.
Use the tracker to create a query http://dev.laptop.org/query. This for example creates a query for [http://dev.laptop.org/query?status=assigned&status=new&status=reopened&component=sugar&order=priority&col=id&col=summary&col=status&col=owner&col=type&col=milestone 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 do it 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.
[[Category:BugSquad]]
[[Category:BugSquad]]