Assuring Quality and Velocity during the Development Cycle via Acceptance Criteria (General Session)
Registered by
Jason Warner
A session to go over the new acceptance criteria in more depth.
Blueprint information
- Status:
- Not started
- Approver:
- Jason Warner
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Whiteboard
The Ubuntu Engineering team will be applying acceptance criteria to upstream code DEVELOPED BY CANONICAL. Again, for 12.04 this will apply only to upstream code developed by Canonical.
The goal of the acceptance criteria is to ensure that code being accepted from Canonical upstreams does not stop Ubuntu from being usable during the development release, and as a result, everyone developing 12.04 should be able to maintain a high degree of development velocity throughout the cycle.
In this session, we will present and discuss the acceptance criteria as currently described in the specification.
(?)
