Planning

Differences between revisions 166 and 168 (spanning 2 versions)
Revision 166 as of 2010-01-27 15:22:47
Size: 7115
Editor: joshuahoover
Comment:
Revision 168 as of 2010-02-09 15:20:32
Size: 7162
Editor: pc-146-76-162-190
Comment:
Deletions are marked like this. Additions are marked like this.
Line 14: Line 14:
|| [[UbuntuBugDay/20100128|2010-01-28]] || ubuntuone-client || || JoshuaHoover || || [[https://wiki.ubuntu.com/UbuntuBugDay/20100211|20100211]]  || Pitivi || || ShaneFagan ||
Line 17: Line 17:
|| || Pitivi || || ShaneFagan ||
Line 39: Line 38:
|| [[UbuntuBugDay/20100128|2010-01-28]] || UbuntuOne-Client || 214 ||

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

20100211

Pitivi

ShaneFagan

network-manager

update-manager

ubiquity

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. Bugs marked for expiration - List of expirable bugs

  5. Hug days for each new default application before they are included in a release of Ubuntu.
  6. Kernel bugs with patches attached (How to handle Kernel bugs with patches)

  7. Packages with a lot of apport crashes

Previous Bug Days

Date

Focus

Bugs Hugged

2010-01-28

UbuntuOne-Client

214

20100114

Gnome Power Manager

174

20091217

Bugs without a package

113

20091210

Compiz

134

20091203

Translations

18

20091112

Nautilus

73

20091105

Gwibber

48

20091014

Server bug day

155

20091008

Confirmed Bugs without a package

59

20090917

No Package bugs

28

20090910

Firefox-3.5

15

20090903

Network-Manager

147

20090827

Totem

30

20090820

Rhythmbox

53

20090813

Notify-OSD

71

20090730

Nautilus

61

20090723

Evolution

79

20090716

Synaptic

132

20090630

Empathy + MSN Support (Butterfly)

24

20090625

Banshee

73

20090618

Empathy

34

20090611

Update-Manager/Notifier

67

20090528

Thunderbird

20

20090521

Firefox 3.0

20090514

New bugs without a package

104

20090507

Compiz

41

20090430

catch new bugs for SRUs and Karmic

43

20090409

Bugs with Patches

44

20090402

Xorg

43

20090319

cups

57

20090312

samba

65

20090305

flashplugin-nonfree

58

20090226

apport-failed-retrace

71

20090219

network-manager-applet

81

20090212

Bugs without a package

125

20090205

update-manager

48

20090129

Compiz

~150

20090122

Firefox 3

~400

20090115

NetworkManager

120

Archive


CategoryBugSquad UbuntuBugDay/Organizing

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