20081104
|
⇤ ← Revision 1 as of 2008-10-31 20:38:23
Size: 2737
Comment:
|
Size: 3095
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 5: | Line 5: |
| This week's Hug Day will focus on bugs without a package since Intrepid came out! | This week's Hug Day will focus on New bugs without a package since Intrepid came out! |
| Line 11: | Line 11: |
| During hug days you can also participate in [[https://wiki.ubuntu.com/5-A-Day|5-A-Day]! To identify your work as part of the hug day follow these steps: | During hug days you can also participate in [[https://wiki.ubuntu.com/5-A-Day|5-A-Day]]! To identify your work as part of the hug day follow these steps: |
| Line 18: | Line 18: |
| == Stock Responses == | == Guidance == |
| Line 21: | Line 21: |
| For problem specific Stock Responses see: [[Bugs/Responses]] | Our goal is to at a minimum assign these bug reports to the correct package. Ideally, we will start gathering detailed information regarding the bug too. For helpful hints regarding which package to assign a bug report to see [[ReportingBugs]]. You can find package specific debugging information at [[DebuggingProcedures|Debugging Central]]. ## For problem specific Stock Responses see: [[Bugs/Responses]] |
| Line 26: | Line 32: |
| * Verify the bug is still not fixed | * Assign the bug to the correct package |
This week's Hug Day will focus on New bugs without a package since Intrepid came out!
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 rowbgcolor=. This will let people know that the bug in that row has been hugged.
5-a-day-ing
During hug days you can also participate in 5-A-Day! To identify your work as part of the hug day follow these steps:
- 5-a-day --add-tag hugday-20081104
- Add bugs to 5-a-day as usual
- And when done with hug day run: 5-a-day --remove-tag hugday-20081104
Guidance
Our goal is to at a minimum assign these bug reports to the correct package. Ideally, we will start gathering detailed information regarding the bug too.
For helpful hints regarding which package to assign a bug report to see ReportingBugs.
You can find package specific debugging information at Debugging Central.
112 New Bugs
To mark it off the list you should:
- Assign the bug to the correct package
Request any needed info, Subscribe, Status to incomplete or
- Set status to Confirmed
Bug |
Subject |
Triager |
37 Incomplete Bugs
To mark it off the list you should:
Change the bug's status to "Confirmed" or "Triaged" if the reporter replied with enough information or
- Ask a secondary follow up question and subscribe to the bug report
Bug |
Subject |
Triager |
40 Confirmed Bugs
To mark it off the list you should:
- Verify the bug is still not fixed
- Request any needed info, Subscribe, Status to incomplete or
Set status to triaged UbuntuBugControl
Bug |
Subject |
Triager |
Progress
More Bugs
This list is just a nibble of the bigger picture.
UbuntuBugDay/20081104 (last edited 2008-11-06 10:28:12 by 139)