...
- Initially all candidate issues for Fedora 3.4 should have Fedora 3.4 as the "Fix version(s)"
- At the start of a milestone
- Review any newly-submitted issues, and either
- Assign to "Fix version(s)" Fedora 3.4 if appropriate, and open; or
- Assign to a future fix version if appropriate, and open; or
- Close/won't fix if appropriate; or
- Leave as submitted if not possible to make a decision
- Prioritise all issues in "Fedora 3.4"
- Move highest-priority issues into next milestone
- Ensure all issues in next milestone are assigned
- Ensure all issues in next milestone have a tester assigned
- Review workload, add more issues from "Fedora 3.4" or move issues back to "Fedora 3.4" until milestone looks do-able
- Review any newly-submitted issues, and either
- During the milestone
- Work on issues, according to who's assigned
- At the end of the milestone
- Ensure completed items have been tested
- Ensure completed items are marked completed
- Move any unstarted issues back to "Fedora 3.4"
- Move any work-in-progress items to the next milestone
To do: can we have a hierarchical "Fix version(s)" structure, ie Fedora 3.4->Milestone 1; or should we use a separate custom "Milestone" field?
Candidate timetable
Candidate timetable
Weeks run from Tuesday through to Monday of the following week, to coincide with the regular Committers Meeting on Tuesday of each week, during which activites of the previous week can be reviewed, and activities for the coming week can be planned.
Week | Deadline | Activity | ||
Apr 20 (Tue) - Apr 26 (Mon) | Mon 26 April - | |||
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 Apr 27 (Tue) - May 3 (Mon) |
| Work on Milestone 1 items 26 Apr | ||
May 4 (Tue) - May 10 (Mon) |
| Work on Milestone 1 items | ||
May 11 (Tue) - May 17 (Mon) | Mon 17 May | 03 May | Friday - Milestone 1 | Work on Milestone 1 items |
10 May May 18 (Tue) - May 24 (Mon) |
| Work on Milestone 2 items | ||
17 May May 25 (Tue) - May 31 (Mon) |
| Work on Milestone 2 items | ||
Jun 1 (Tue) - Jun 7 (Mon) | Mon 7 Jun | 24 May | Friday - Milestone 2 | Work on Milestone 2 items 31 May |
Jun 8 (Tue) - Jun 14 (Mon) |
| Work on Milestone 3 items | ||
07 Jun Jun 15 (Tue) - Jun 21 (Mon) |
| Work on Milestone 3 items | ||
Jun 22 (Tue) - Jun 28 (Mon) | Mon 28 Jun | 14 Jun | Friday - Milestone 3 - RC Code Freeze (code freeze) | Work on Milestone 3 items |
Jun 29 (Tue) - Jul 5 (Mon) | Fri 2 Jul - RC release | 21 Jun | Friday - RC Release | Release week - final testing and release 28 Jun |
Jul 6 (Tue) - Jul 12 (Mon) |
| Keep clear, week before OR2010 | ||
05 Jul |
| OR2010 | ||
OR2010 5-9 Jul | ||||
Jul 13 (Tue) - Jul 19 (Mon) 12 Jul |
| RC testing (community) | ||
19 Jul Jul 20 (Tue) - Jul 26 (Mon) |
| RC testing (community) | ||
26 Jul Jul 27 (Tue) - Aug 2 (Mon) |
| Bug fixes | ||
02 Aug Aug 3 (Tue) - Aug 9 (Mon) |
| Bug fixes | ||
Aug 10 (Tue) - Aug 16 (Mon) | Fri 13 Aug | 09 Aug | Friday - 3.4 Release | Release week - final testing and release |