3,267
edits
Changes
Jump to navigation
Jump to search
Line 37:
Line 37: + + + + + + + + + + + + + + + + + + + + +
BugSquad/Triage Guide (view source)
Revision as of 06:34, 25 September 2008
, 06:34, 25 September 2008→Steps of Triaging
== 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]].
=== Verify that the bug is not a duplicate ===
Many times the particular bug has already been reported into our bug tracking system. Note to which bug this is a duplicate to and close this one with 'resolve as duplicate'. If the original bugs needs further information, please encourage the reporter to provide that information there.
=== 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]].
=== 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 :)
=== If the bug is in an obsolete version of the application ===
Sugar developers may not work anymore on the specified version. If you are unsure if that is the case, please ask at #sugar or in the mailing list.
=== If the bug is not in Sugar ===
The bug might not be in sugar and in one of the libraries sugar is using (i.e. telepathy). Please try to help to get the bug report upstream. Also ensure that both bug reports contain a link to each other.
[[Category:BugSquad]]
[[Category:BugSquad]]