20100227

This week's Hug Day will focus on Ubiquity!

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)):

  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

Stock Responses

For problem specific Stock Responses see: Bugs/Responses

Special Notes

  • If the bug happens when you test it you can run ubiquity -d and attach the logs on failure using ubuntu-bug bugnumber
  • Do not mark bugs as duplicates or close bugs that do not have a log or a response.

### 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:

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.


CategoryBugSquad

UbuntuBugDay/20100227 (last edited 2010-03-01 10:01:39 by anzenketh)