Planning

Differences between revisions 275 and 276
Revision 275 as of 2011-07-07 12:25:56
Size: 5382
Editor: pedro
Comment:
Revision 276 as of 2011-07-26 14:12:15
Size: 5464
Editor: pedro
Comment:
Deletions are marked like this. Additions are marked like this.
Line 14: Line 14:
|| 20110616 || Totem || || pedro ||
|| 20110714 || GNOME Control Center || || pedro ||
Line 41: Line 39:
|| [[https://wiki.ubuntu.com/UbuntuBugDay/20110616|20110616]] || Totem || ||
|| [[https://wiki.ubuntu.com/UbuntuBugDay/20110714|20110714]] || GNOME Control Center || ||

This is a simple wiki page to have a list of upcoming UbuntuBugDays.

Be sure to check out https://launchpad.net/ubuntu/+upstreamreport along with the old Bug Day Focus history, this will make the choosing of future focuses easier.

If you want to help to organize a Bug day, please look at the Organizing Page

When arranging a Hug Day it is quite helpful to get developer(s) of the package involved. Developer Responsibilities is a good reference for finding out whom to contact.

Proposed Bug Days

Date

Focus

Comments

Organizer

Unity

20110811

Translations

Gabor Kelemen

firefox

2500 bugs across 3 source pacakges (need to update wiki guides first)

micahg

network-manager

Natty focus packages

Would like to reserve 1? bug days per month to focus on packages key to Natty release in time for being able to fix and ship with Natty. Packages and timing to be determined based on post UDS planning.

skaet

Your Idea Here!

Comments?

Your Name Here

Ideas

  1. < persia> Another idea would be to do a day for patch integration: there's lots of bugs with patches out there. Perhaps have a day where a couple people offer a quick -classroom session on testing/applying/requesting upload for patches every 4-6 hours, and people chase the list of bugs with the patch flag set.

    1. bdmurray has some stuff that will help here

  2. < persia> Something else we used to do for fun was keyword bugdays.

    1. < persia> One of my favorite was "time".

    2. < persia> Basically, pick a word, and do a bugsearch with the word. Find one with about the right number of bugs.

  3. tagging bugs hug day, create multiple pools of bugs that need to be tagged, example: mark as bitesize the bugs with patches that need to generate a debdiff in order to get bug fixed.
  4. Hug days for each new default application before they are included in a release of Ubuntu.
  5. Kernel bugs with patches attached (How to handle Kernel bugs with patches)

  6. Packages with a lot of apport crashes

  7. Papercut bugs to review.

Previous Bug Days

Date

Focus

Bugs Hugged

20110616

Totem

20110714

GNOME Control Center

20110609

Nautilus

20110602

Evolution

20110526

Compiz

20110414

ubuntu-translations

20110415

iso testing bugs

20110407

update-manager

20110406

Unity

20110324

ubiquity

20110310

Edubuntu

20110303

usb-creator

20110224

Unity

20110203

Rhythmbox

51

20110210

LibreOffice

45

20110127

Totem

79

20110120

Pidgin

110

20110113

empathy

102

20110106

Gwibber

80

Archive


CategoryBugSquad UbuntuBugDay/Organizing

UbuntuBugDay/Planning (last edited 2016-07-11 22:43:55 by tsimonq2)