TaskTemplate
|
Size: 2710
Comment: attmept #2
|
← Revision 44 as of 2010-06-29 12:52:52 ⇥
Size: 4567
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 7: | Line 7: |
| 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. | After you have triaged or fixed a bug put your '''Launchpad Id''' 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. |
| Line 9: | Line 9: |
| == Tools == For doing your work easier during the hug days remember to use the [[https://wiki.ubuntu.com/UbuntuBugDay/Tools|hugday-tools]]. |
|
| Line 11: | Line 14: |
| During hug days you can also do [[https://wiki.ubuntu.com/5-A-Day|5-A-Day]] for this one you can do the following in order to tag your work on the hug day: | |
| Line 13: | Line 15: |
| * 5-a-day --add-tag hugday-<<<DATE>>> * Add bugs to 5-a-day as usual * And when done with hug day run: 5-a-day --remove-tag hugday-<<<DATE>>> |
To sign up for 5-A-Day participation, please add your Launchpad ID to the Participants column. (This is not the email address you used for signing up for LP, but the last part of the URL that https://launchpad.net/people/+me redirects you to (everything behind the ~ sign)): |
| Line 17: | Line 17: |
| 1. Click on https://launchpad.net/people/+me 2. Look at the URL bar, everything behind the ~ sign is your Launchpad ID. Also sign up here: https://launchpad.net/~5-a-day-participants/+join == Upstream project == ## If the project is an upstream one please add the link to that particular bug tracker and home page of the project here. The '''<<<TARGET>>>''' upstream Bug Tracker and Home page are: * Bug Tracker * Home Page Please check for already bugs filed in the upstream Bug tracker before sending our reports. |
|
| Line 22: | Line 36: |
| Line 33: | Line 46: |
| Line 40: | Line 52: |
| Line 53: | Line 64: |
| == ### Bugs with Patches == '''To mark it off the list you should:''' * Verify if the patch really is a patch. * If it is not, unmark it as a patch. * If it is, get the bug triaged and looked by the maintainer. |
|
| Line 54: | Line 71: |
| ||<rowbgcolor="#FFEBBB"> '''Bug''' || '''Subject''' || '''Triager''' || == ### Bugs to be forwarded Upstream == '''To mark it off the list you should:''' * Verify the bug is still not fixed * Search in the [[https://wiki.ubuntu.com/Bugs/Upstream/|Upstream bug tracker]] for a similar report, if there is no one, open a new report and add a [[https://wiki.ubuntu.com/Bugs/Watches|Bug watch]] to the downstream report. * Set status to triaged [[UbuntuBugControl]] ||<rowbgcolor="#FFEBBB"> '''Bug''' || '''Subject''' || '''Triager''' || == ### Private bugs to be reviewed == '''To mark it off the list you should:''' * [[UbuntuBugControl]] verify that the report does not contains sensitive data. * If it does not, Change the Visibility status to Public. * If the report does contains sensitive data, add a comment explaining on why it will keep on the Private status. ||<rowbgcolor="#FFEBBB"> '''Bug''' || '''Subject''' || '''Triager''' || |
|
| Line 58: | Line 94: |
| ## example - attachment:compiz-1day-new.png | ## example - {{attachment:compiz-1day-new.png}} |
| Line 60: | Line 96: |
| {{http://people.ubuntu.com/~brian/complete-graphs/<<<TARGET>>>/plots/<<<TARGET>>>-1day-triaging.png}} | {{http://people.ubuntu.com/~brian/complete-graphs/TARGET/plots/TARGET-1day-triaging.png}} |
| Line 65: | Line 101: |
| This list is just a nibble of the [[https://bugs.launchpad.net/ubuntu/+source/<<<TARGET>>>|bigger picture]]. | This list is just a nibble of the [[https://bugs.launchpad.net/ubuntu/+source/TARGET|bigger picture]]. |
This week's Hug Day will focus on <<<TARGET>>>!
After you have triaged or fixed a bug put your Launchpad Id 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.
Tools
For doing your work easier during the hug days remember to use the hugday-tools.
5-a-day-ing
To sign up for 5-A-Day participation, please add your Launchpad ID to the Participants column. (This is not the email address you used for signing up for LP, but the last part of the URL that https://launchpad.net/people/+me redirects you to (everything behind the ~ sign)):
Click on https://launchpad.net/people/+me
- Look at the URL bar, everything behind the ~ sign is your Launchpad ID.
Also sign up here: https://launchpad.net/~5-a-day-participants/+join
Upstream project
The <<<TARGET>>> upstream Bug Tracker and Home page are:
- Bug Tracker
- Home Page
Please check for already bugs filed in the upstream Bug tracker before sending our reports.
Stock Responses
For problem specific Stock Responses see: Bugs/Responses
### New 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 Confirmed
Bug |
Subject |
Triager |
### 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 |
### 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 |
### Bugs with Patches
To mark it off the list you should:
- Verify if the patch really is a patch.
- If it is not, unmark it as a patch.
- If it is, get the bug triaged and looked by the maintainer.
Bug |
Subject |
Triager |
### Bugs to be forwarded Upstream
To mark it off the list you should:
- Verify the bug is still not fixed
Search in the Upstream bug tracker for a similar report, if there is no one, open a new report and add a Bug watch to the downstream report.
Set status to triaged UbuntuBugControl
Bug |
Subject |
Triager |
### Private bugs to be reviewed
To mark it off the list you should:
UbuntuBugControl verify that the report does not contains sensitive data.
- If it does not, Change the Visibility status to Public.
- If the report does contains sensitive data, add a comment explaining on why it will keep on the Private status.
Bug |
Subject |
Triager |
Progress
More Bugs
This list is just a nibble of the bigger picture.
UbuntuBugDay/TaskTemplate (last edited 2010-06-29 12:52:52 by pc-231-206-161-190)