Page History

Previous: 0.26
Next: 0.30

Status

• 12 November 2013: Trunk is open at revision 1541273

Issues

...

Changes to the release branch require approval. The approval has two parts:

• Review by a developer other than the original contributor
• Approval by the release manager

To request a change after beta, post your request to the mailing list. Put "RFI" (request for inclusion) and the requested release in the subject. Make sure the change has a JIRA, so the reviewer and release manager can record their approvals, rejections, or other comments there.

...

Change acceptance criteria

• 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 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 February, 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 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

RC2: 19 March, 1 week later

RC3: 26 March, 1 week later

• Targeted release date