Announcing the Next Ubuntu Bug Day!
ag.restringere at gmail.com
Sun Mar 17 00:12:31 UTC 2013
Given these two items:
- Verify the bug is still not fixed
How do you quickly verify if the problem has been fixed?
What is the process to be used?
-Request any needed info
What is the specific log(s) and information needed?
On Sat, Mar 16, 2013 at 6:00 PM, Fabio Marconi <marconifabio at hotmail.it>wrote:
> Announcing the Next Ubuntu Bug Day! - 21 March 2013
> Fellow Ubuntu Triagers!This week's Bug Day target is *drum roll please* ubuntu-release-upgrader ! * 59 New bugs need a hug * 8 Incomplete bugs need a status check * 21 Confirmed bugs need a review
> Bookmark it, add it to your calendars, turn over those egg-timers! * 21 march 2013 * http://wiki.ubuntu.com/UbuntuBugDay/Ubuntu-release-upgrader-20130321Are you looking for a way to start giving some love back to your adorable Ubuntu Project?Did you ever wonder what Triage is? Want to learn about that?This is a perfect time!, Everybody can help in a Bug Day!open your IRC Client and go to #ubuntu-bugs (FreeNode) the BugSquad will be happy to help you to start contributing!We are always looking for new tasks or ideas for the Bug Days, if you have oneadd it to the Planning page https://wiki.ubuntu.com/UbuntuBugDay/PlanningIf you're new to all this, head to http://wiki.ubuntu.com/BugsHave a nice day, Marconi Fabio[From the BugSquad]
> Ubuntu-bugsquad mailing list
> Ubuntu-bugsquad at lists.ubuntu.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ubuntu-bugsquad