Ubuntu Wiki

**DRAFTING IN PROGRESS**

Kernel Bug Migration

Beginning with the Hardy Heron 8.04 LTS release the Ubuntu kernel source package naming convention changed from 'linux-source-2.6.xx' to just 'linux'. Going forward, all kernel bugs will be reported against the [https://launchpad.net/ubuntu/+source/linux/ linux] package. It is important to the Ubuntu QA and Kernel Team that bugs open against older kernels that still exist in the current development kernel be carried forward. This wiki will document the process that will be followed as this transition is made.

Process

There are thousands of bugs open against older Ubuntu kernels (~2800 to be exact). It will be a time consuming process to move bugs forward manually. A better method would be to automate the process. This could be done through the use of a python-launchpad-bugs script. Process details that could be automated are to be outlined and discussed below:

1. The script will automatically post a stock reply (see below)
2. The script will flip the linux-source-2.6.xx task to "Incomplete"
3. Should the script automatically add the 'linux' task?
   1. If so, what should the Status be set to? "Incomplete"?
   2. Does python-launchpad-bugs even provide the ability to add new tasks to an existing bug report? I seem to recall the last time I tried to script this sort of thing plb did not provide this sort of functionality.
   3. The reason I ask this question is that asking bug reporters to test the latest kernel and then additionally add the 'linux' task to their bug report if the issue still remains may be bit much to ask all at once. The more work we can automate for the bug reporter the simpler their bug report migration will be.

   4. kiko commented that instead of adding the 'linux' package we could just change the task from linux-source-2.6.xx -> linux and then include the package name in the stock reply . . . "It appears this bug is still open against an older Ubuntu kernel (linux-source-2.6.22)". However, we would then lose bug's "history" being reflected in the task info table.

Criteria

Document how we will determine which bugs to automatically carry forward with the process outlined above. Note, we must be able to determine this criteria in an automated fashion as well.

1. Bug must be open against a linux-source-2.6.xx package and not undergoing the SRU process. (ie Status is New, Incomplete, Confirmed, Triaged, In Progress, Fix Committed)
2. Bug does not already have a 'linux' task
3. Bug will not have had any recent activity in the past 6? weeks.
4. Bug is not a High or Critical bug - we should look at the High and Critical bugs manually

Stock Reply

This is a suggested reply to be posted to open older kernel bugs. Please note the following issues regarding this stock reply:

• this reply won't be helpful for update/upgrade bugs - can't test those via a LiveCD as suggested in the stock reply
• this reply won't be helpful for xen kernel bugs
• Hibernate - can't test via LiveCD as suggested in the stock reply (can only test Suspend via LiveCD)
• Also keep in mind that bugs will be open against multiple kernel packages. We don't want to spam the bug multiple times. One solution would be to tag the bug say "kernel-migration" the first time we stock reply to know we've already posted a comment.

Beginning with the Hardy Heron 8.04 development cycle, the Ubuntu kernel source package naming convention changed from 'linux-source-2.6.xx' to just 'linux'.  Going forward, all Ubuntu kernel bugs will be reported against the 'linux' source package.  It appears this bug is still open against an older Ubuntu kernel.  It is important that this bug be carried forward if this issue still exists in the latest Ubuntu kernel release.  It would be helpful if you could verify if this issue still exists.  You should be able to test the latest Ubuntu kernel release from a LiveCD which can be downloaded from http://cdimage.ubuntu.com/releases/hardy/ .  Please let us know your results.  More information regarding the Ubuntu kernel bug migration can be found at  https://wiki.ubuntu.com/QATeam/KernelBugMigration .  We appreciate your patience and understanding as we make this transition.  Thanks!

How detailed do we want this stock reply to be? The concern I have with adding more information to the stock reply is that it will get overwhelming for the bug reporter to read through all the details.

But if for example we are not automatically adding the 'linux' task for them, would it be good to include the following?:

{{{If this bug still exists in the latest kernel release, please add the 'linux' task to this bug report. This can be done by:

1) Click the "Also affect distribution" link in the "Actions" area of this bug report. 2) Set the "Distribution:" to "Ubuntu" 3) Type in "linux" (no quotes) as the "Source Package Name:" 4) Click "Continue" }}}

Additionally, if the bug no longer exists do we want to explain how they can manage their own bug report status to flip the report from "Incomplete" to an appropriate resolved status?:

If this is no longer an issue, please update the bug report status.  You can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status .

Proposal 2 (heno)

This approach assume sthe following:

• If the bug already has a 'linux' task do nothing, but record the bug number for later inspection
• To 2.6.xx bugs, add a 'linux' task and set it to incomplete.
• Close the 2.6.xx tasks as Won't fix.
• Tag the bug "kernel-migration".

Beginning with the Hardy Heron 8.04 development cycle, the Ubuntu kernel source package naming convention changed from 'linux-source-2.6.xx' to just 'linux'.  Going forward, all Ubuntu kernel bugs will be reported against the 'linux' source package.  It appears this bug is still open against an older Ubuntu kernel.  It is important that this bug be carried forward if this issue still exists in the latest Ubuntu kernel release.  

A new 'linux' package task has been added and the older 'linux-source-2.6.xx' task closed. It would be helpful if you could verify if this issue still exists on Hardy.  For most issues you can test with the latest Ubuntu kernel release from a LiveCD which can be downloaded from http://cdimage.ubuntu.com/releases/hardy/ .  

If you can confirm the existance of this bug on Hardy, please change the status to confirmed and provide updated debugging information from following. If you can confirm that it is fixed, please mark it as fix released. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status .

More information regarding the Ubuntu kernel bug migration can be found at  https://wiki.ubuntu.com/QATeam/KernelBugMigration .  We appreciate your patience and understanding as we make this transition.  Thanks!

Todo

Document what needs to be done and when.