[Ubuntu Wiki] Update of "Bugs/HowToTriage" by ddecator
Ubuntu Wiki
noreply at ubuntu.com
Sun Jul 11 20:58:11 BST 2010
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification.
The following page has been changed by ddecator:
http://wiki.ubuntu.com/Bugs/HowToTriage?action=diff&rev1=129&rev2=130
The comment on the change is:
Changed the style to better match /BugSquad, will email ML to get feedback on whether to keep the changes or not
------------------------------------------------------------------------------
<<Include(Bugs/BugsHeader)>>
- ||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents>>||
+ ||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;">Contents<<BR>> 1. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Bug%20Types|Bug Types]]<<BR>> 1. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Apport%20reports|Apport reports]]<<BR>> 1. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Apport%20crash%20reports|Apport crash reports]]<<BR>> 2. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Confirmed%20bugs|Confirmed bugs]]<<BR>> 3. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Feature%20Requests|Feature Requests]]<<BR>> 4. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Regressions|Regressions]]<<BR>> 5. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Untriaged%20bugs|Untriaged bugs]]<<BR>> 6. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Bug%20reports%20not%20in%20English|Bug reports not in English]]<<BR>> 7. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Special%20types%20of%20bugs|Special types of bugs]]<<BR>> 1. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Developer%20Process%20Bugs|Developer Process Bugs]]<<BR>> 2. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Needs%20Packaging%20Bugs|Needs Packaging Bugs]]<<BR>> 3. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Security%20Bugs|Security Bugs]]<<BR>> 4. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Translation%20Bugs%20and%20Launchpad%20integration|Translation Bugs and Launchpad integration]]<<BR>> 2. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Actions|Actions]]<<BR>> 1. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Confirming|Confirming]]<<BR>> 2. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Forwarding%20upstream|Forwarding upstream]]<<BR>> 1. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Marking%20a%20Bug%20as%20Requiring%20Forwarding|Marking a Bug as Requiring Forwarding]]<<BR>> 3. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Marking%20duplicate|Marking duplicate]]<<BR>> 4. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Improving%20a%20bug%20report|Improving a bug report]]<<BR>> 5. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Invalidating|Invalidating]]<<BR>> 3. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Status%20and%20Importance|Status and Importance]]<<BR>> 4. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Looking%20through%20your%20bugs|Looking through your bugs]]||
In a hospital, triage happens the instant a patient arrives through the emergency room doors. His vital signs are checked, his status assessed, and he gets sorted in amongst all the other patients waiting for treatment.
@@ -14, +14 @@
Working on simple, untriaged bugs is a good way to get started and become acquainted with the triaging procedure since you'll have to deal with every aspect of the life cycle of a bug. The section [[#untriaged|Untriaged bugs]] explains where to find them.
- = Bug types =
+ <<Anchor(Bug Types)>>
+ ||<tablestyle="width:50%;" style="width: 40px; border: none; -moz-border-radius-topleft: 15px ;-moz-border-radius-bottomleft: 15px; background-color: #F1F1DD;text-align: left;">{{attachment:bugsquad.png}}||<style="width: 90%; border: none; -moz-border-radius-topright: 15px;-moz-border-radius-bottomright: 15px; text-align: left; font-size: 1.8em; background-color: #F1F1DD;" >'''Bug Types'''||
== Apport reports ==
@@ -82, +83 @@
Once tagged, the bugs will appear on the [[http://qa.ubuntu.com/reports/regression/regression_tracker.html|regression tracking page]] and will from there be escalated to the development teams. See [[QATeam/RegressionTracking]] for more information.
- <<Anchor(untriaged)>>
== Untriaged bugs ==
Untriaged bugs are bugs that haven't been touched by any triager yet. These bugs were reported and have yet to be touched since.
@@ -171, +171 @@
Apart from opening the 'ubuntu-translations' task to let the [[Translations]] team know the bug exists the bug should be handled like any bug. When its status in the 'ubuntu' project is [[#Confirmed_bugs|set to 'Triaged']] they know the report is ready for them to work on.
- = Actions =
+ <<Anchor(Actions)>>
+ ||<tablestyle="width:50%;" style="width: 40px; border: none; -moz-border-radius-topleft: 15px ;-moz-border-radius-bottomleft: 15px; background-color: #F1F1DD;text-align: left;">{{attachment:actions.png}}||<style="width: 90%; border: none; -moz-border-radius-topright: 15px;-moz-border-radius-bottomright: 15px; text-align: left; font-size: 1.8em; background-color: #F1F1DD;" >'''Actions'''||
Below are some common actions you will perform while Triaging. The [[https://launchpad.net/launchpad-gm-scripts |Launchpad Greasemonkey scripts]] can be a great time-saver while performing the below actions!
@@ -195, +196 @@
The 'Triaged' status is used to show you are done with triaging the bug. Only members of the Ubuntu Bug Control team can set this status. Only set this status if the cause of the bug has been found and the developers can start fixing the problem right away.
- <<Anchor(Forwarding_upstream)>>
== Forwarding upstream ==
Forwarding bugs upstream is an important part of being a triager. Without telling them, upstream developers might never know of the bug you've been triaging so studiously.
@@ -249, +249 @@
----
CategoryBugSquad
- <<Anchor(Improving_a_bug_report)>>
== Improving a bug report ==
Only valid and well described bugs can be processed efficiently and swiftly by the developers. A small guide at [[Bugs/Improving]] helps with handing over a good bug to the developers when setting the status 'Triaged'.
@@ -266, +265 @@
<<Include(Bugs/Responses, , from="^== Incomplete bugs without a response from submitter ==", to="==")>>
- = Status and Importance =
+ <<Anchor(Status and Importance)>>
+ ||<tablestyle="width:50%;" style="width: 40px; border: none; -moz-border-radius-topleft: 15px ;-moz-border-radius-bottomleft: 15px; background-color: #F1F1DD;text-align: left;">{{attachment:importance.png}}||<style="width: 90%; border: none; -moz-border-radius-topright: 15px;-moz-border-radius-bottomright: 15px; text-align: left; font-size: 1.8em; background-color: #F1F1DD;" >'''Status and Importance'''||
The default meanings of Importances and Statuses are explained at [[Bugs/Importance]] and [[Bugs/Status]]. Make sure you've read these pages thoroughly.
If in doubt, the maintainer (or the one working on the bug) should change the Status and Importance. It usually reflects the status of this work or reflects how the bug fits into her/his working time.
- = Looking through your bugs =
+ <<Anchor(Looking through your bugs)>>
+ ||<tablestyle="width:50%;" style="width: 40px; border: none; -moz-border-radius-topleft: 15px ;-moz-border-radius-bottomleft: 15px; background-color: #F1F1DD;text-align: left;">{{attachment:bugsquad.png}}||<style="width: 90%; border: none; -moz-border-radius-topright: 15px;-moz-border-radius-bottomright: 15px; text-align: left; font-size: 1.8em; background-color: #F1F1DD;" >'''Looking through your bugs'''||
Perhaps you want to look at a list of bugs you are working on to see if anyone has replied and to make sure you haven't forgotten one.
More information about the Ubuntu-bugsquad
mailing list