Planning

Differences between revisions 279 and 280
Revision 279 as of 2013-01-15 18:53:27
Size: 5217
Editor: om26er
Comment:
Revision 280 as of 2013-01-15 18:58:29
Size: 5217
Editor: om26er
Comment:
Deletions are marked like this. Additions are marked like this.
Line 14: Line 14:
|| 20130115 || Transmission BT Bugs || Rebooting UBDs || Omer Akram (om26er) || || 20130117 || Transmission BT Bugs || Rebooting UBDs || Omer Akram (om26er) ||

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

20130117

Transmission BT Bugs

Rebooting UBDs

Omer Akram (om26er)

20110908

Bugs without a package

20110825

Ubuntu Software Center Bugs

USC need a little TLC.

Evan Peck (brokenfingers)

DATEDATE

Idea

Extra info/Reason

Author (lpusername)

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)