KernelBugMigration

Differences between revisions 5 and 51 (spanning 46 versions)
⇤ ← Revision 5 as of 2008-02-19 00:57:32 →
Size: 4984
Editor: c-67-160-148-53
Comment: add criteria items
← Revision 51 as of 2013-02-22 23:42:22 → ⇥
Size: 6075
Editor: javier-lopez
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
**DRAFTING IN PROGRESS** <<Include(QATeam/Header)>>

||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents>>||
Line 4: Line 7:
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 be carried forward. This wiki will document the process that will be followed as this transition is made. 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.
Line 7: Line 10:
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: 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: Line 12:
 1. The script will automatically post a stock reply (see below)
 1. The script will flip the linux-source-2.6.xx task to "Incomplete"
 1. Should the script automatically add the 'linux' task?
  1. If so, what should the Status be set to? "Incomplete"?
  1. 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.
  1. 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. 		 1. Launchpad janitor will automatically post a stock reply depending on which kernel is being processed (see below)
  1. Temporarily disable sending emails to ubuntu-kernel-team (if subscribed to bug report) to avoid spamming the kernel team mailing list
 1. 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
 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. 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.
 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. 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 release.
Line 17: Line 19:
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. 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.
Line 19: Line 21:
 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)
 1. Bug will not have had any recent activity in at least 6? weeks.		  1. Bug is not undergoing the SRU process (ubuntu-sru is not a subscriber and the bug is not specifically targeted to a release)
 1. Bug is not a security bug (security_related is false)
 1. Bug must be against a linux-source-2.6.xx package and have a Status of either New, Incomplete, Confirmed, or Triaged
 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 in this first pass)
 1. Bug does not already have a "linux" task (just reiterating above)
 1. Bug is not a High or Critical bug - we should look at the High and Critical bugs manually
 1. Bug is not In Progress or Fix Committed - these should be looked at manually too as they may really be fixed
Line 23: Line 30:
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.
 '''Stock Reply for 2.6.15'''
Line 31: Line 32:
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 kernel bugs will be reported against the 'linux' source package. It appears this bug is still open against an older kernel. It is important that this bug be carried forward if this issue still exists in the latest kernel release. It would be helpful if you could verify if this bug exists in the latest kernel release. You should be able to test the latest kernel release from a LiveCD which can be downloaded from here: http://cdimage.ubuntu.com/releases/hardy/ . Please let us know your results. More information regarding the kernel bug migration can be found here: https://wiki.ubuntu.com/QATeam/KernelBugMigration . We appreciate your patience and understanding as we make this transition. Thanks! Beginning with the Hardy Heron 8.04 development cycle, 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. Also, if you would be interested in testing the upcoming Intrepid Ibex 8.10 release, it is available at http://www.ubuntu.com/testing . Please let us know your results. Thanks!
Line 34: Line 35:
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"		 '''Stock Reply for 2.6.17'''
{{{
The 18 month support period for Edgy Eft 6.10 has reached its end of life. As a result, we are closing the linux-source-2.6.17 Edgy Eft kernel task. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . 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 46: Line 40:
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?:
 '''Stock Reply for 2.6.20 and 2.6.22'''
Line 49: Line 42:
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 [WWW] https://wiki.ubuntu.com/Bugs/Status . Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . 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 52: Line 45:
== Timeline ==
Document what will be done and when.		 == Todo ==
Document what needs to be done and when.
Line 55: Line 48:
||Task||Completion Date||
||Create [:QATeam/KernelBugMigration] wiki that documents what is being done and why||TBD||		 ||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 ||In Progress - ogasawara||
||Find the [[https://devpad.canonical.com/~brian/kernel-bug-querying.html|count of New, Incomplete, Confirmed, and Triaged]] bugs open against a single kernel release which will be affected - probably a database query||June 9, 2008||Done - bdmurray||
||Find the average # of subscribers each affected bug has - probably a database query||TBD||In Progress - bdmurray||
||Live run of Launchpad-janitor||TBD||Launchpad Team||

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 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:

  1. Launchpad janitor will automatically post a stock reply depending on which kernel is being processed (see below)
    1. Temporarily disable sending emails to ubuntu-kernel-team (if subscribed to bug report) to avoid spamming the kernel team mailing list
  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 release.

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.

  1. Bug is not undergoing the SRU process (ubuntu-sru is not a subscriber and the bug is not specifically targeted to a release)
  2. Bug is not a security bug (security_related is false)
  3. Bug must be against a linux-source-2.6.xx package and have a Status of either New, Incomplete, Confirmed, or Triaged
  4. 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)
  5. Bug does not already have a "linux" task (just reiterating above)
  6. Bug is not a High or Critical bug - we should look at the High and Critical bugs manually
  7. Bug is not In Progress or Fix Committed - these should be looked at manually too as they may really be fixed

Stock Reply

Stock Reply for 2.6.15 

Beginning with the Hardy Heron 8.04 development cycle, 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.  Also, if you would be interested in testing the upcoming Intrepid Ibex 8.10 release, it is available at http://www.ubuntu.com/testing .  Please let us know your results.  Thanks!

Stock Reply for 2.6.17 

The 18 month support period for Edgy Eft 6.10 has reached its end of life. As a result, we are closing the linux-source-2.6.17 Edgy Eft kernel task. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing .  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, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package.  We are automatically migrating this bug to the new "linux" package.  However, development has already began for the upcoming Intrepid Ibex 8.10 release.  It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing .  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 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

In Progress - ogasawara

Find the count of New, Incomplete, Confirmed, and Triaged bugs open against a single kernel release which will be affected - probably a database query

June 9, 2008

Done - bdmurray

Find the average # of subscribers each affected bug has - probably a database query

TBD

In Progress - bdmurray

Live run of Launchpad-janitor

TBD

Launchpad Team

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