...
Status
- 13 June 2013: 0.22 is generally available
- 3 June 2013: RC6 is approved for release
- 26 May 2013: Proposed final RC6 is available at revision 1486100
- 22 May 2013: Proposed final RC5 is available at revision 1485215
- 16 May 2013: Proposed final RC4 is available at revision 1483543
- 9 May 2013: RC3 is available at revision 1480717 of the release branch
- 23 April 2013: RC2 is available at revision 1470549 of the release branch
- 5 April 2013: RC1 is available at revision 1464657 of the release branch
- 24 March 2013: Beta is available at revision 1460488 of the release branch
- 24 March 2013: The release branch is created at revision 1460483
- 11 March 2013: Alpha is cut at revision 1455236 of trunk
- 19 February 2013: Alpha is postponed to 4 March
- 19 November 2012: Trunk is open for 0.22 development at revision 1411381
Issues
Features and improvements | http://s.apache.org/qpid-0.22-improvements![]() |
Open bugs | http://s.apache.org/qpid-0.22-open-bugs![]() |
Fixed bugs | http://s.apache.org/qpid-0.22-fixed-bugs![]() |
Candidate bugs | http://s.apache.org/qpid-0.22-candidate-bugs![]() |
Distributions
Links
Release branch | https://svn.apache.org/repos/asf/qpid/branches/0.22/![]() |
Release tag | https://svn.apache.org/repos/asf/qpid/tags/0.22/![]() |
Announce mail |
Criteria for accepting changes at each stage of the release
- 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
- RC1, RC2, ..., GA: Bug fixes for important defects only, such as build failures, regressions, or security vulnerabilitities
Schedule
13 February 4 March
- Alpha
- 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
27 February 18 March, 2 weeks later
- Beta
- The release branch is created
- Trunk opens for development toward the next release
- Release branch commits require approval
- Release manager produces outstanding bug report and triages bugs
13 March 1 April, 2 weeks later
- RC1
- Documentation is staged for release
- Preliminary release notes are available for comment
20 March 8 April, 1 week later
- RC2
27 March 15 April, 1 week later
- RC3
- Targeted release date