TaskTemplate

Differences between revisions 17 and 20 (spanning 3 versions)
Revision 17 as of 2007-07-03 23:50:15
Size: 3691
Editor: 65-102-54-112
Comment: formatting changes
Revision 20 as of 2008-01-11 19:00:08
Size: 1104
Editor: c-71-59-213-167
Comment: Revamping
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
Here we have a sampling of bugs to work on for Hug Day. After you have triaged or fixed a bug put your name in the last column and set the row background to a green color by adding '''lightgreen;''' in the first cell of the column after "background-color:". This will let people know that the bug in that row has been worked on. Here we have a sampling of bugs to work on for Hug Day. After you have triaged or fixed a bug put your name in the last column and set the row's background to green by adding '''lightgreen''' in the first cell of the column after "background-color:" and before ";". This will let people know that the bug in that row has been hugged.
Line 5: Line 5:
== 50 bugs in status "Incomplete" without an owner ==
These bugs may just need to be rejected as they have been marked "Incomplete" but nobody may be watching them. There are about #### [https://launchpad.net/ubuntu/+bugs?field.searchtext=&orderby=-date_last_updated&search=Search&field.status%3Alist=Incomplete&assignee_option=none&field.assignee=&field.bug_reporter=&field.bug_contact=&field.component-empty-marker=1&field.status_upstream-empty-marker=1&field.omit_dupes.used=&field.omit_dupes=on&field.has_patch.used=&field.tag=&field.has_cve.used=&field.has_no_package.used=&start=2175 unowned bugs].
## the start=2175 should be manipulated to pick something not too recent maybe even the last page is best
## repeat as necessary for each unique type of bug
== XYZ bugs in status or importance ==
Description of what kind of bugs are they and how can people find more?
Line 9: Line 9:
## Here be goals for these bugs
Line 16: Line 17:
## query used
## ./bugnumbers -l "https://launchpad.net/ubuntu/+bugs?field.searchtext=&orderby=-date_last_updated&search=Search&field.status%3Alist=Incomplete&assignee_option=none&field.assignee=&field.bug_reporter=&field.bug_contact=&field.component-empty-marker=1&field.status_upstream-empty-marker=1&field.omit_dupes.used=&field.omit_dupes=on&field.has_patch.used=&field.tag=&field.has_cve.used=&field.has_no_package.used=&start=2175" > bugs-wo-owner.txt
## the start=2175 should be manipulated to pick something not too recent
## head -n 25 bugs-wo-owner.txt | perl -pe 's/^(\d+)[^\(]*\([^\)]+\)\s*-\s*(.*)/\|\|<rowstyle="background-color: ;"> \[http:\/\/launchpad.net\/bugs\/$1 $1\] \|\| $2 \|\| \|\|/'
Line 21: Line 18:
== 50 bugs without a package ==
These bugs were just reported against Ubuntu which means they are less likely to get attention. There are about #### [https://launchpad.net/ubuntu/+bugs?field.searchtext=&orderby=-datecreated&search=Search&field.status%3Alist=New&field.importance%3Alist=Undecided&field.assignee=&field.owner=&field.omit_dupes=on&field.has_patch=&field.has_no_package=on bugs] in this state.
'''To mark it off the list you should:'''
 * Assign it to a package and mark it "Confirmed" '''or'''
 * Assign it to a package, ask a question, mark it "Incomplete" and assign it to yourself '''or'''
 * Search for duplicates (and mark if found) '''or'''
 * Reject it for a good reason

|| Bug || Subject || Triager ||
## query used
## ./bugnumbers -l "https://launchpad.net/ubuntu/+bugs?field.searchtext=&orderby=-datecreated&search=Search&field.status%3Alist=New&field.importance%3Alist=Undecided&field.assignee=&field.owner=&field.omit_dupes=on&field.has_patch=&field.has_no_package=on -m 120000 > bugs-wo-package.txt"
## 120000 is an arbitrary number depending on how many bugs we currently have
## magic wiki formatting done by:
## head -n 50 bugs-wo-package.txt | perl -pe 's/^(\d+)[^\(]*\([^\)]+\)\s*-\s*(.*)/\|\|<rowstyle="background-color: ;"> \[http:\/\/launchpad.net\/bugs\/$1 $1\] \|\| $2 \|\| \|\|/'
## where 50 is a reasonable number of bugs to touch
----
CategoryTemplate

Here we have a sampling of bugs to work on for Hug Day. After you have triaged or fixed a bug put your name in the last column and set the row's background to green by adding lightgreen in the first cell of the column after "background-color:" and before ";". This will let people know that the bug in that row has been hugged.

XYZ bugs in status or importance

Description of what kind of bugs are they and how can people find more?

To mark it off the list you should:

  • Ask the reporter if it is still an issue, assign it to yourself and mark it "Incomplete" or

  • Set it "Confirmed" and set an importance (if you are not a QA member ask someone for help) or

  • Search for duplicates (and mark if found) or

  • Reject it due to no response

Bug

Subject

Triager


CategoryTemplate

UbuntuBugDay/TaskTemplate (last edited 2010-06-29 12:52:52 by pc-231-206-161-190)