Return of the Ubuntu Server papercuts
During the Lucid development cycle, we decided to create a Server papercuts project, to translate our increased focus on QA and polish into real actions. This project focused on identifying and fixing lots of minor annoyances, low-hanging-fruit bugs that traditionally get less attention than others. It was successful enough that we decided to pursue it during the Maverick cycle… so here it comes, the Return of the Ubuntu Server papercuts (with a vengeance).
We’ll run this effort during the first three development iterations. The biggest change since the Lucid Server papercuts is that we start before FeatureFreeze this time, so small new features or behavior changes are accepted, too ! And the first iteration (Alpha-2 subcycle) starts… now.
It’s time to nominate your personal pet bug, your favorite minor annoyance, your preferred Server PITA ! Here is the process to follow:
- If the papercut isn’t already filed as an Ubuntu bug in Launchpad, file a bug against the affected Ubuntu package
- Look up the bug you want to nominate as a Server papercut, then click on “Also affects project”
- Click “Choose another project” and type in “server-papercuts”, click “Continue”
- Click on “Add to Bug report”
That’s it ! Your bug will now show up on the Server papercuts buglist and we’ll triage and select them during the next Ubuntu Server meeting, Tuesday June 1st, 1800 UTC on IRC channel #ubuntu-meeting on Freenode. Our goal is to have a list of 16 candidates for this iteration.
What makes a good Server papercut ?
- Bug affects a server package
- Bug has an obvious and easy fix
- Bug makes the life of the sysadmin more miserable
What doesn’t make a good Server papercut ?
- Large-scale improvements that affect multiple packages
- Your solution is likely to result in a new papercut for someone else