...
- Trunk open to Alpha: Developers work at their own discretion
- Alpha to Beta: Major features, improvements, or refactorings need discussion before they can go in; bug fixes are unencumbered
- Beta to RC1: Bug fixes only; exceptions are sometimes made for important improvements that are isolated and small in terms of code delta
- After RC1: Bug fixes for important defects only, such as build failures, regressions, or security vulnerabilitities
Schedule
Alpha: 12 19 February
- Major feature integration ends; with approval, certain less disruptive features can be committed
- Trunk remains open for bug fixing
- The alpha release tests the release process after the introduction of major features
Beta: 26 February5 March, 2 weeks later
- The release branch is created
- Release branch commits require approval
- Trunk opens for development toward the next release
RC1: 12 March, 2 weeks 1 week later
- Documentation is staged for release
- Preliminary release notes and documentation are available for review
- Release manager produces outstanding bug report
- Only important defects are considered for inclusion
...
0.28 Release 