Differences between revisions 4 and 5
Revision 4 as of 2010-02-25 23:44:49
Size: 5636
Editor: cpe-66-69-226-228
Revision 5 as of 2010-02-25 23:47:48
Size: 5658
Editor: cpe-66-69-226-228
Deletions are marked like this. Additions are marked like this.
Line 70: Line 70:
  * same as Tuesday, rolling toward a "final" release   * same as Tuesday, rolling toward a "final" release by the end of the day


The Anecdote

When I was a kid, we had one of these things hanging outside, an eerie blue light called a "bug zapper". Some bugs were hopelessly draw to it, would fly into the light, and be electrocuted, leaving a nasty smell of ozone behind.

I see nowadays there's a more proactive approach -- an electrically charged tennis racket, also called a "bug zapper":

For many server packages in Ubuntu, we simply wait around for bugs to be fixed. Sometimes they get fixed upstream. Sometimes someone drives by and drops off a patch. It's like waiting for the bugs to hurl themselves at the blue light.

Release Note

During Beta1 and Beta2, the Ubuntu Server Community triaged and fixed XXX bugs during a concentrated push to solidify several sets of key server packages (foo, bar, baz).


Given Lucid's LTS status, we should take a more proactive approach to fixing Ubuntu Server bugs. We should arm a platoon of Ubuntu Server Developers and Community Members with electric rackets, and send them out on timed, coordinated missions, focusing all efforts on a particular package or group of packages for about a week at a time.

User Stories

== Assumptions ==

Some care needs to be taken around freezes. Also, it would be helpful to get participation from the QA team as well as the community.


As an example, several members of the Server Team and Community focused on fixing Eucalyptus bugs (and only Eucalyptus bugs) for a short period. In October 2009, we uploaded the Ubuntu eucalyptus package 10 times, fixing 60 bugs.



This snippet is lifted from the LucidReleaseSchedule, and indicates all relevant freezes.


Date (Monday)






March 1st


Virtualization: qemu-kvm, libvirt, lxc, virt-manager

Warning /!\ UserInterfaceFreeze


March 8th

File/Print sharing: samba

Warning /!\ Beta1Freeze, Warning /!\ KernelFreeze


March 15th


Databases: postgres, mysql

Warning /!\ Beta1Release

Beta 1


March 22nd

MathiasGug, DustinKirkland

UEC: eucalyptus, euca2ools

Warning /!\ DocumentationStringFreeze

April 2010


March 28th

Warning /!\ Beta2Freeze


April 5th

Warning /!\ Beta2Release

Beta 2


  • Monday - total bug triage
    • prioritize all bugs according to a defined formula for that package, generally:
      • Critical = data loss, corruption, or serious security problem

      • High = totally prevents the package from functioning, workarounds impractical

      • Medium = most bugs, non-ideal behavior, perhaps workarounds prevent from being 'high'

      • Low = other bugs, with workarounds, affecting fewer users

      • Wishlist = cosmetic, feature requests, nice-to-have's

    • confirm/reproduce any bugs in the "new" state
    • triage any bugs in the confirmed state, ie, identify the problem, test workarounds or solutions
    • expire any bugs that are invalid
    • fix-release any bugs that cannot be reproduced on the latest code
    • assign yourself (or others) triaged bugs that they can fix
    • time permitting, start working on fixes
  • Tuesday
    • bzr branch the latest lucid code
    • work on fixes, pushing to lp:~yourname/thepackage/bugnumber
    • build a package in your PPA for testing
    • get some else to verify your PPA build
    • uploader will roll all fixes into an upload for that day
  • Wednesday
    • same as Tuesday
  • Thursday
    • same as Tuesday, rolling toward a "final" release by the end of the day
  • Friday
    • Comprehensive regression testing
    • Generate status report on total uploads, bugs triaged, bugs fixed, participation
    • Post to ubuntu-server@ mailing list, ubuntu-server blog


  • Communication: #ubuntu-server in IRC
  • Bazaar:
  • PPA for uploads and testing

For that package, do the following:

  • Tuesday - Friday
    • - working from bzr branches, the specified Uploaders merge fixes from the Zappers - prepare a package upload to Lucid (or to a Proposed PPA, depending on how far into the Lucid Cycle we are) - packages build with elevated priority (ideally) - All Uploaders and Zappers test the new package, confirming each other's fixes, and ensure there are no regressions - If the package was in a PPA for testing, now the Uploader pushes it to Karmic
  • Friday
    • - Generate a report
      • + from the package(s) changelogs, showing the number of uploads and bugs fixed in those packages that week + the LP bug list before and after triaging

Unresolved Issues


ServerLucidBugZapping (last edited 2010-03-05 14:43:26 by lns-bzn-48f-81-56-218-246)