Diff for "QATeam/KernelBugMigration"

KernelBugMigration

Differences between revisions 25 and 28 (spanning 3 versions)

**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 the launchpad-janitor. Process details are outlined and discussed below:

Launchpad janitor will automatically post a stock reply depending on which kernel task is being processed (see below)
linux-source-2.6.15 bugs will be renamed to the new 'linux' kernel package.
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.
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.

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.

Bug is not undergoing the SRU process.
Bug must be against a linux-source-2.6.xx package and have a Status of either "New", "Incomplete", or "Confirmed"
Bug must only be tasked to a single linux-source-2.6.xx package (ie bugs against multiple kernel releases will not be handled)
Bug does not already have a "linux" task (just reiterating above)
Bug is not a High or Critical bug - we should look at the High and Critical bugs manually
Bug is not In Progress or Fix Committed - these should be looked at manually too as they may really be fixed
Bug is not a security bug

Stock Reply

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".  All open Ubuntu kernel bugs need to be reported against the "linux" kernel package.  We are automatically migrating this linux-source-2.6.15 kernel bug to the new "linux" package.  We appreciate your patience and understanding as we make this transition.  Thanks!

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 by changing the Status of the "linux" task from "Incomplete" to "New".  We appreciate your patience and understanding as we make this transition.  Thanks!

Stock Reply for 2.6.20 and 2.6.22

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".  All open Ubuntu kernel bugs need to be reported against the "linux" kernel package.  It appears this bug is still open against an older Ubuntu kernel.  We are automatically migrating this bug to the new "linux" package.  It would be helpful if you could test the new Hardy Heron 8.04 release and verify if this is still an issue - http://www.ubuntu.com/getubuntu/download .  If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New".  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)

-  ⇤ ← Revision 25 as of 2008-05-20 13:23:15 → 
  Size: 8379
  Editor: 161
  Comment:
+   ← Revision 28 as of 2008-05-20 22:04:06 → ⇥
  Size: 4920
  Editor: 194
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 7:
-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 launchpad.  Process details are outlined and discussed below:
+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 the launchpad-janitor.  Process details are outlined and discussed below:
 Line 9:
-. Launchpad will automatically post a stock reply depending on which kernel task is being processed (see below)
 1. linux-source-2.6.15 bugs will be renamed to the new 'linux' kernel package
 1. linux-source-2.6.17 bugs will be closed as "Won't Fix" as the support period has ended
 1. linux-source-2.6.20 and linux-source-2.6.22 bugs will be marked as "Incomplete" and
+. Launchpad janitor will automatically post a stock reply depending on which kernel task is being processed (see below)
 1. linux-source-2.6.15 bugs will be renamed to the new 'linux' kernel package.
 1. 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.
 1. 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.
 Line 17:
-. 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)
 1. Bug does not already have a 'linux' task
+. Bug is not undergoing the SRU process.
 1. Bug must be against a linux-source-2.6.xx package and have a Status of either "New", "Incomplete", or "Confirmed"
 1. Bug must only be tasked to a single linux-source-2.6.xx package (ie bugs against multiple kernel releases will not be handled)
 1. Bug does not already have a "linux" task (just reiterating above)
-Line 21:
+Line 23:
-. Bug is not a secuity bug
+. Bug is not a security bug
-Line 24:
+Line 26:
-This is a suggested reply to be posted to open older kernel bugs.  Please note the following issues regarding this:

 * 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.
-Line 30:
+Line 28:
-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!
+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".  All open Ubuntu kernel bugs need to be reported against the "linux" kernel package.  We are automatically migrating this linux-source-2.6.15 kernel bug to the new "linux" package.  We appreciate your patience and understanding as we make this transition.  Thanks!
-Line 35:
+Line 33:
-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.
+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 by changing the Status of the "linux" task from "Incomplete" to "New".  We appreciate your patience and understanding as we make this transition.  Thanks!
-Line 47:
+Line 38:
-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!
+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".  All open Ubuntu kernel bugs need to be reported against the "linux" kernel package.  It appears this bug is still open against an older Ubuntu kernel.  We are automatically migrating this bug to the new "linux" package.  It would be helpful if you could test the new Hardy Heron 8.04 release and verify if this is still an issue - http://www.ubuntu.com/getubuntu/download .  If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New".  We appreciate your patience and understanding as we make this transition.  Thanks!
-Line 56:
+Line 40:
-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!
}}}