Revision 1 as of 2009-04-24 22:30:10
initial draft for 20090428 kernel bug day
add ref to http://qa.ubuntu.com/reports/ogasawara/kernel-bugday/20090428.html
|Deletions are marked like this.||Additions are marked like this.|
|Line 70:||Line 70:|
|Please refer to the following for the list of bugs to focus on for this bug day:
Canonical Kernel Team Bug Day
The focus of today's bug day will be a combination of bugs with patches as well as old incomplete bugs. Each developer has a list below of 20 bugs to focus on. There is also a community section for anyone else wanting to help out. The goal will be to handle the bugs accordingly:
Bugs With Patches
- Confirm the bug does indeed have a patch attached
- Evaluate if the patch is upstream or subsequently in the latest Ubuntu kernel.
- If the patch is not upstream, inquire why (see Stock Reply)
- If the patch is upstream but not in Ubuntu kernel, cherry-pick. Determine if also SRU worthy.
- If the patch is already available in a released Ubuntu kernel mark Fix Released.
Old Incomplete Bugs
- If the last comment is more than 6 weeks old and they have not supplied the requested information, close as Won't Fix (see Stock Reply)
- If they have supplied the requested information make sure they've tested with the latest Jaunty release (see Stock Reply)
- If they've confirmed the issue exists with the latest Jaunty release, move bug from Incomplete to Triaged (or In Progress if you want to work on the bug).
Here are references to some useful tools that may help you more efficiently process the list of bugs.
This is a collection of greasemonkey scripts which Launchpad users and Ubuntu developers have found useful. For the purpose of Bug Day's, the stockreplies gm-script will be the most useful. The stockreplies script allows you to save custom comments to insert into bug reports and additionally set the status and importance of a bug at the same time.
The launchpadlib library depends on wadllib, another open-source library released by the Launchpad team. Get a copy of the launchpadlib and wadllib source with bzr and install it.
$ bzr branch lp:wadllib $ cd wadllib $ sudo ./setup.py install
Then do the same for launchpadlib.
$ bzr branch lp:launchpadlib $ cd launchpadlib $ sudo ./setup.py install
After installation you can write custom scripts to manipulate bug reports. This is useful for dealing with a list of bugs which all require the same type of actions/comment. For example, here is a stock-reply.py script which reads a list of bugs from a "stock.txt" file, posts a standard comment to each bug, transitions the status to Incomplete, and subscribes oneself to the bug report. It's quicker to use a launchpadlib script for this rather than having to do a page load per bug in order to use the greasemonkey stockreplies.
Here's some common stock replies that may apply to some of the bugs:
Bug with Patch not Upstream
This patch does not appear to be upstream. It created a siginificant amount of extra work for the Ubuntu kernel team to maintain out of tree patches. As such they typicaly require patches to be submitted and accepted upstream first. Do you know if the patch referenced here has gone upstream? Please let us know. Thanks.
- Set status to Incomplete
This bug report is being closed because we received no response to the last inquiry for information. Please reopen it if this is still an issue in the current Ubuntu release, Jaunty Jackalope 9.04. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks.
- Set status to Won't Fix
Unfortunately it seems this bug is still an issue. Can you confirm this issue exists with the most recent Jaunty Jackalope 9.04 release - http://www.ubuntu.com/news/ubuntu-9.04-desktop . Please let us know your results. Thanks.
- Set status to Incomplete
Please refer to the following for the list of bugs to focus on for this bug day: