Improve security update QA
Registered by
Caroline Ford
on 2006-09-18
We should revisit our current QA process for security updates to avoid regressions (such as the recent broken kernel update). This should at least involve peer review and a defined test procedure.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Whiteboard
(?)