8,288
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: − + − + − = Bugsquad Triage Guide = + + Line 8:
Line 9: − + − + Line 18:
Line 19: − + + + + − + − + − + Line 34:
Line 38: − + Line 42:
Line 46: − + − + Line 56:
Line 60: − + − + − − −
no edit summary
{{TeamHeader|BugSquad}}
<noinclude>{{TeamHeader|BugSquad}}{{TOCright}}
[[Category:BugSquad]]
[[Category:HowTo]]
</noinclude>
== Why bug triaging is helpful? ==
== Why bug triaging is helpful? ==
* Verify that the bug is filed against the correct component
* Verify that the bug is filed against the correct component
* Verify that the bug has the correct software version field
* Verify that the bug has the correct software version field
* Verify the priority of the bug
* Verify the severity of the bug
== How to get up to speed ==
== How to get up to speed ==
=== Create a trac account ===
=== Create a trac account ===
* Create a trac account at [http://dev.sugarlabs.org/register dev.sugarlabs.org].
* Create a trac account at [https://bugs.sugarlabs.org/register bugs.sugarlabs.org].
=== Join the sugar-devel mailing list ===
=== Join the sugar-devel mailing list ===
=== Read the Stock Responses ===
=== 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.
The [[BugSquad/Triage Guide/Stock Responses]] 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.
=== Read the Status Fields ===
The [[BugSquad/Status Fields]] describe the fields you can use to triage the bugs in Trac.
== Triaging ==
== Triaging ==
=== 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 and read it carefully.
Use the tracker to [https://bugs.sugarlabs.org/query create a query]. This for example creates a query for [https://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=sugar&order=priority&col=id&col=summary&col=status&col=type&col=priority all open sugar bugs]. Choose one you want to triage and read it carefully.
=== Find what should be changed===
=== Find what should be changed===
Read the [[BugSquad/TriageGuide#Steps_of_Triaging]] to determine what should be changed (if anything) and how.
Read the [[BugSquad/Triage Guide#Steps of Triaging]] to determine what should be changed (if anything) and how.
=== Ask someone to verify your changes ===
=== 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 [[BugSquad/Contacts#List_of_Triagers]]. You will find them usually at #sugar on freenode.
For the first bugs we encourage you to make the changes in conjunction with a member of the BugSquad team [[BugSquad/Contacts#Squad Members]]. You will find them usually at #sugar on freenode.
=== Make your changes ===
=== Make your changes ===
== Steps of Triaging ==
== Steps of Triaging ==
These are some notes how to triage the bugs in detail. In all the cases you can find the matching stock response at [[BugSquad/TriageGuide/StockResponses]].
These are some notes how to triage the bugs in detail. In all the cases you can find the matching stock response at [[BugSquad/Triage Guide/Stock Responses]].
=== Verify that the bug is not a duplicate ===
=== Verify that the bug is not a duplicate ===
=== The bug report need some logs ===
=== The bug report need some logs ===
In most of the cases the developer could use some logs to better identify the problem. Instructions on how to take logs are at [[BugSquad/GetLogs]].
In most of the cases the developer could use some logs to better identify the problem. Instructions on how to take logs are at [[BugSquad/Get Logs]].
=== If the bug is not described well ===
=== If the bug is not described well ===
The bug report isn't very useful if the bug isn't described well. Some people do not read the [[BugSquad/BugHowto]] or are just inexperienced. Best, is to use one of the stock answers and go to the next bug :)
The bug report isn't very useful if the bug isn't described well. Some people do not read the [[BugSquad/Bug Report]], [[olpc:Reporting bugs]], or are just inexperienced. Best, is to use one of the stock answers and go to the next bug :)
=== If the bug is in an obsolete version of the application ===
=== If the bug is in an obsolete version of the application ===
The bug might not be in sugar and in one of the libraries sugar is using (e.g. telepathy). Please try to help to get the bug report upstream. Also ensure that both bug reports contain a link to each other.
The bug might not be in sugar and in one of the libraries sugar is using (e.g. telepathy). Please try to help to get the bug report upstream. Also ensure that both bug reports contain a link to each other.
=== Priority of the bug ===
=== Severity of the bug ===
Verify that the priority of the bug is set correctly. What you should not try to set is the milestone of the bugs, this is the duty of the component maintainer.
Verify that the severity of the bug is set correctly. What you should not try to set is the milestone and the priority of the bugs, this is the duty of the component maintainer. (Please refer to [[BugSquad/Status_Fields#Severity_.28Default.3DUnspecified.29|Severity]] for a definition of the severity fields.)
[[Category:BugSquad]]