...
- Break down the release into milestones
- Schedule work items against milestone
- Work items should be prioritised
- When scheduling, concentrate on the next milestone, scheduling all uncompleted items in order of priority
- Ensure all scheduled items have a responsibility against them; review milestone schedule against developer's availability and adjust as necessary
- Review priorities of outstanding items when milestone is complete and schedule the next milestone
Candidate timetable
Date (week commencing) | Deadline | Activity |
29 Mar |
| Release preparation/planning |
05 Apr |
| Release preparation/planning |
12 Apr | Friday - Milestone 1 scheduled | Release preparation/planning |
19 Apr |
| Work on Milestone 1 items |
26 Apr |
| Work on Milestone 1 items |
03 May | Friday - Milestone 1 | Work on Milestone 1 items |
10 May |
| Work on Milestone 2 items |
17 May |
| Work on Milestone 2 items |
24 May | Friday - Milestone 2 | Work on Milestone 2 items |
31 May |
| Work on Milestone 3 items |
07 Jun |
| Work on Milestone 3 items |
14 Jun | Friday - Milestone 3 - RC Code Freeze | Work on Milestone 3 items |
21 Jun | Friday - RC Release | Release week - final testing and release |
28 Jun |
| Keep clear, week before OR2010 |
05 Jul |
| OR2010 |
12 Jul |
| RC testing (community) |
19 Jul |
| RC testing (community) |
26 Jul |
| Bug fixes |
02 Aug |
| Bug fixes |
09 Aug | Friday - 3.4 Release | Release week - final testing and release |