Juju QA release planning
Registered by
Curtis Hovey
How often do we release? Time-based to feature based milestones?
How do we select bugs and features for development and stable releases?
How do we choose a revision to release? CI revision blessing?
The Juju project tends to have a *next* milestone and a *future* at all times, yet many other High bugs are being worked on every week. It is difficult to see the general plan to deliver complete features by the end of the 6 month goal.
Engineers currently work quickly near the release date to deliver features and fixes, then a revision is selected for release. This will change when CI can bless a revision. Do we delay releases or choose to releases older revisions?
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Curtis Hovey
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
- Katherine Cox-Buday
Whiteboard
(?)
