Review of the Stable Maintenance Process
Look over the current process for stable kernel maintenance and identify places to improve the process or make it simpler to understand for people trying to get things changed for released kernels.
Blueprint information
- Status:
- Complete
- Approver:
- Pete Graner
- Priority:
- Essential
- Drafter:
- Steve Conklin
- Direction:
- Approved
- Assignee:
- Steve Conklin
- Definition:
- Approved
- Series goal:
- Accepted for natty
- Implementation:
-
Implemented
- Milestone target:
-
ubuntu-11.04
- Started by
- Steve Conklin
- Completed by
- Steve Conklin
Whiteboard
Status:
Documentation updates are complete. The testing parts of the process are now in place and producing results. We have run the process twice through to release successfully. Testing blueprint is now made and other items are tracked there.
Work Items for natty-alpha-1:
[sconklin] boiler plate text for bug closure on failure to verify:DONE
[kate.stewart] workout the sru schedule with respect linaro and platform:DONE
[sconklin] provide a document that describes the process, bug tracking, and which tests are being performed, etc:DONE
[pitti] ensure verification bug update indicates that unverified patches are going to be pulled: DONE
[sconklin] process to add the bug to the changelog manually during release process:DONE
[jibel] QA team - define a mechanism to assign the proposed upload tracking bug to them and track results:DONE
[leannogasawara] provide info from HWDB http://
[jeremyfoshee] make sure that the bugs that we are sending for this are on the dashboard:DONE
Work items for natty-alpha-2:
[vtuson] HW Cert team - provide a description of what testing they provide, and an idea of the number of hours required to run those:DONE
[vtuson] to investigate which systems are "common" for cert testing:DONE
[vtuson] blueprint for cert-team:DONE
[brad-figg] look at arsenal scripts to nag bug owners to validate their fixes or lose them:DONE
