Kernel Bug Migration
leann.ogasawara at canonical.com
Mon Jun 9 23:42:05 UTC 2008
As most of you know, beginning with the Hardy release cycle the Ubuntu
kernel source package naming convention changed from linux-source-2.6.xx
to just linux. I think it is important that as we move forward we be
sure to migrate any bugs open against older kernels to the most recent
kernel. Otherwise, I fear bugs may stagnate and go unaddressed. There
is a significant amount of bugs open against older Ubuntu kernels.
Manually processing all these bugs by hand would be inefficient. I'd
like to propose automating the process of moving some of these bugs
forward. I've documented the process, criteria, and stock replies I'd
like to use at the following wiki:
I'll inline portions of the wiki below.
1. Bug is not undergoing the SRU process (ubuntu-sru is not a
subscriber and the bug is not specifically targeted to a
2. Bug is not a security bug (security_related is true)
3. Bug has less than or equal to (<=) 10 subscribers
4. Bug must be against a linux-source-2.6.xx package and have a
Status of either New, Incomplete, Confirmed, or Triaged
5. Bug must only be tasked to a single linux-source-2.6.xx package
(ie bugs against multiple kernel releases will not be handled in
this first pass)
6. Bug does not already have a "linux" task (just reiterating
7. Bug is not a High or Critical bug - we should look at the High
and Critical bugs manually
8. Bug is not In Progress or Fix Committed - these should be looked
at manually too as they may really be fixed
1. Launchpad janitor will automatically post a stock reply (see
wiki) depending on which kernel is being processed
2. linux-source-2.6.15 bugs will be renamed to the new "linux"
kernel package. Also, tag these 'linux-source-2.6.15' to
maintain package history
3. linux-source-2.6.17 bugs will be closed as Won't Fix as the 18
month support period has ended. The new "linux" task will be
added but marked as Incomplete. See stock reply for more info.
Also, tag these 'linux-source-2.6.17' to easily list which bugs
were migrated and isolate possible candidates to close if we've
received no response for testing with the latest release.
4. linux-source-2.6.20 and linux-source-2.6.22 bugs will be marked
as Won't Fix. The new "linux" task will be added but marked as
Incomplete. See stock reply for more info. Also, tag these
'linux-source-2.6.20' or 'linux-source-2.6.22' to easily list
which bugs were migrated and isolate possible candidates to
close if we've received no response for testing with the latest
I'd appreciate any feedback you guys may have. Ideally I'd like to
start moving forward with this beginning in July.
More information about the kernel-team