BugTriage
|
Size: 2647
Comment:
|
← Revision 25 as of 2012-06-19 00:49:02 ⇥
Size: 1692
Comment: Fix typo
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| * [[Kernel/BugTriage/BugStates]] -- how the Kernel team uses bug states * [[Kernel/TriageLevels]] -- how the various levels of triage are defined and how they are performed * [[Kernel/Tagging]] -- how tags are used within Kernel bugs * [[Kernel/Tagging]] -- Level-2 triage tags and searches * [[KernelTeam/UsingArsenal]] -- utilising the kernel arsenal scripts for automated triage * [[Kernel/BugTriage/CollectingInformation]] -- what information to collect for specific bug types * [[Kernel/Debugging]] -- debugging hints for various common scenarios |
This is a single, jump off point for all questions about how the Kernel Team deals with LaunchPad bugs. |
| Line 11: | Line 6: |
| = Triage Effort = | For an introduction to Triage we recommend you start by reading [[Kernel/BugTriage/Process]]: |
| Line 13: | Line 8: |
| Triaging kernel bugs is a day-to-day effort, and can be very time consuming. Luckily, we have a lot of community members willing and able to help with this effort. The kernel team will also begin using a set of [[https://code.edge.launchpad.net/~arsenal-devel|Kernel Arsenal scripts]] to help with the day-to-day triaging efforts (see [[KernelTeam/UsingArsenal]]). In order to make sure everyone working on kernel bugs follows the same policy, this document will describe how to handle the kernel bug workflow. This will also provide bug reporters with an idea of the life cycle their bug will follow. | For additional information see: |
| Line 15: | Line 10: |
| Note that beginning with the Karmic development cycle an emphasis is being made to ensure bugs are tested and reported upstream. In relation to this, the Ubuntu kernel team will be transitioning their focus to fixing bugs which have been confirmed to exist upstream or are fixed upstream but exist in the Ubuntu kernel. | || [[Kernel/FAQTriage | FAQ ]] || Frequently Asked Questions about kernel bug processing. || || [[Kernel/BugTriage/Process | Process ]] || What Kernel bug triage is all about. || || [[Kernel/BugTriage/BugStates | Bug States ]] || How the Kernel Team interprets a bugs status. || || [[Kernel/TriageLevels | Triage Levels ]] || How the various levels of triage are defined and how they are performed || || [[Kernel/Tagging | Bug Tags ]] || How tags are used within Kernel bugs, Level-2 triage tags and searches || || [[Kernel/BugTriage/CollectingInformation | Collecting Information ]] || The information to collect for specific bug types. || || [[Kernel/BugTriage/Responses | Standard Responses ]] || Standard responses to put on bugs for various circumstances || || [[Kernel/Debugging | Debugging Techniques ]] || Debugging hints for various common scenarios || || [[Kernel/BugDay | Bug Days ]] || Date of the next Bug Day and what it will be focused on. || |
| Line 17: | Line 20: |
| Also note that, as of the Maverick cycle, we will be breaking out our bugs into specific subsystems based on tags. For a list of current tags, please see the [[Kernel/Tagging|Tagging]] page. For specific information concerning the Bug Review process as it currently stands, please visit the [[Kernel/BugReview|Bug Review page]]. We have also further defined the levels of triage within our team. For an overview of that, please visit the [[Kernel/TriageLevels|Levels of Triage]] page. = Caveats = Sometimes kernel bugs are opened to track security vulnerabilities. These bugs usually contain the word "CVE" either in the title or bug description and will most likely have the '''ubuntu-security''' team subscribed to the bug. We should try to avoid spamming these bugs with comments to test the latest kernel to verify if the issue still exists. Whether manually posting to a bug or using python-launchpad-bugs to script comments, please take extra care to not cause more unnecessary traffic for the security team to deal with. Thanks. |
This is a single, jump off point for all questions about how the Kernel Team deals with LaunchPad bugs.
For an introduction to Triage we recommend you start by reading Kernel/BugTriage/Process:
For additional information see:
Frequently Asked Questions about kernel bug processing. |
|
What Kernel bug triage is all about. |
|
How the Kernel Team interprets a bugs status. |
|
How the various levels of triage are defined and how they are performed |
|
How tags are used within Kernel bugs, Level-2 triage tags and searches |
|
The information to collect for specific bug types. |
|
Standard responses to put on bugs for various circumstances |
|
Debugging hints for various common scenarios |
|
Date of the next Bug Day and what it will be focused on. |
Kernel/BugTriage (last edited 2012-06-19 00:49:02 by 210-185-64-102)