KernelBugMigration

Differences between revisions 22 and 23
Revision 22 as of 2008-05-20 12:50:00
Size: 9384
Editor: 161
Comment:
Revision 23 as of 2008-05-20 13:04:46
Size: 9950
Editor: 161
Comment: add 2.6.15 stock reply
Deletions are marked like this. Additions are marked like this.
Line 40: Line 40:
The 18 month support period for Edgy Eft 6.10 has reached it's end of life. As a result, we are closing the linux-source-2.6.17 Edgy Eft kernel task. However, Hardy Heron 8.04 was recently released. It would be helpful if you could test the new release and verify if this is still an issue - http://www.ubuntu.com/getubuntu/download . If the issue still exists, please update this report to include the "linux" package task. This can be done by doing the following: The 18 month support period for Edgy Eft 6.10 has reached it's end of life. As a result, we are closing the linux-source-2.6.17 Edgy Eft kernel task. However, Hardy Heron 8.04 was recently released. It would be helpful if you could test the new release and verify if this is still an issue - http://www.ubuntu.com/getubuntu/download . If the issue still exists, please update this report to include the "linux" kernel task. This can be done by doing the following:
Line 53: Line 53:
Beginning with the Hardy Heron 8.04 development cycle, the Ubuntu kernel package naming convention changed from "linux-source-2.6.xx" to just "linux". Going forward, all Ubuntu kernel bugs need to be reported against the "linux" kernel package. Additionally, all Ubuntu kernel bugs open against older Ubuntu kernel versions need to be migrated to the newer "linux" kernel package. We are automatically migrating linux-source-2.6.15 kernel bugs to the new "linux" package. We appreciate your patience and understanding as we make this transition. Thanks!
Line 57: Line 58:
Beginning with the Hardy Heron 8.04 development cycle, the Ubuntu kernel package naming convention changed from "linux-source-2.6.xx" to just "linux". Going forward, all Ubuntu kernel bugs need to be reported against the "linux" source package. Additionally, all Ubuntu kernel bugs open against older Ubuntu kernel versions need to be migrated to the newer "linux" kernel package. It appears this bug is still open against an older Ubuntu kernel. It is important that this bug be carried forward to the new "linux" kernel package if this issue still needs to be resolved. It would be helpful if you could test the new release and verify if this is still an issue - http://www.ubuntu.com/getubuntu/download . If the issue still exists, please add the "linux" package task to the bug report. This can be done by doing the following: Beginning with the Hardy Heron 8.04 development cycle, the Ubuntu kernel package naming convention changed from "linux-source-2.6.xx" to just "linux". Going forward, all Ubuntu kernel bugs need to be reported against the "linux" kernel package. Additionally, all Ubuntu kernel bugs open against older Ubuntu kernel versions need to be migrated to the newer "linux" kernel package. It appears this bug is still open against an older Ubuntu kernel. It is important that this bug be carried forward to the new "linux" kernel package if this issue still needs to be resolved. It would be helpful if you could test the new release and verify if this is still an issue - http://www.ubuntu.com/getubuntu/download . If the issue still exists, please add the "linux" kernel package task to the bug report. This can be done by doing the following:

**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 "Won't Fix"
    1. Since 2.6.17 bugs are no longer supported we will begin with this group first.
  3. Decided to request reporter to open linux task and provide detailed instructions on how to do so.
  4. Will use kernel-bug-janitor lp id to automatically close bugs
  5. Will also send email notification to appropriate ml of when this migration will happen and what will be done.

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)
  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
  5. Bug is not In Progress or Fix Committed - these should be looked at manually too as they may really be fixed

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 search if a comment has already been posted by the kernel-bug-janitor.

Stock Reply for 2.6.17

The 18 month support period for Edgy Eft 6.10 has reached it's end of life. As a result, we are closing the linux-source-2.6.17 Edgy Eft kernel task. However, Hardy Heron 8.04 was recently released. It would be helpful if you could test the new release and verify if this is still an issue - http://www.ubuntu.com/getubuntu/download .  If the issue still exists, please update this report to include the "linux" kernel task. This can be done by doing the following:

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"

Thanks in advance.

Stock Reply for 2.6.15

Beginning with the Hardy Heron 8.04 development cycle, the Ubuntu kernel package naming convention changed from "linux-source-2.6.xx" to just "linux".  Going forward, all Ubuntu kernel bugs need to be reported against the "linux" kernel package.  Additionally, all Ubuntu kernel bugs open against older Ubuntu kernel versions need to be migrated to the newer "linux" kernel package.  We are automatically migrating linux-source-2.6.15 kernel bugs to the new "linux" package.  We appreciate your patience and understanding as we make this transition.  Thanks!

Stock Reply for non 2.6.17

Beginning with the Hardy Heron 8.04 development cycle, the Ubuntu kernel package naming convention changed from "linux-source-2.6.xx" to just "linux".  Going forward, all Ubuntu kernel bugs need to be reported against the "linux" kernel package.  Additionally, all Ubuntu kernel bugs open against older Ubuntu kernel versions need to be migrated to the newer "linux" kernel package.  It appears this bug is still open against an older Ubuntu kernel.  It is important that this bug be carried forward to the new "linux" kernel package if this issue still needs to be resolved.  It would be helpful if you could test the new release and verify if this is still an issue - http://www.ubuntu.com/getubuntu/download .  If the issue still exists, please add the "linux" kernel package task to the bug report.  This can be done by doing the following:

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"

We appreciate your patience and understanding as we make this transition.  Thanks!

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.

Task

Completion Date

Notes

Create [:QATeam/KernelBugMigration] wiki that documents what is being done and why

TBD

Investigate if python-launchpad-bugs has functionality to add new tasks

TBD

answer is no - submitted p-l-b bug [https://bugs.launchpad.net/python-launchpad-bugs/+bug/193853 193853]

Manually inspect High and Critical bugs against 2.6.15 and 2.6.22

TBD

In Progress - ogasawara

Manually inspect In Progress and Fix Committed bugs against 2.6.17, 2.6.20 and 2.6.22 kernel

TBD

Find list of bugs to automate Won't Fix'ing - probably a database query(bdmurray)

TBD

Test run of automated script

TBD

Live run of automated script

TBD

QATeam/KernelBugMigration (last edited 2013-02-22 23:42:22 by javier-lopez)