THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Status
- 7 September 2013: Qpid 0.24 is generally available
- 6 September 2013: The vote to release the RC4 bits as final is approved
- 23 August 2013: Proposed final RC4 is out at revision 1516979 of the release branch
- 21 August 2013: Proposed final RC3 is out at revision 1515891 of the release branch
- 13 August 2013: RC2 is available at revision 1513405 of the release branch
- 5 August 2013: RC1 is available at revision 1509744 of the release branch
- 17 July 2013: RC1 is delayed by two weeks
- 17 July 2013: Beta is available at revision 1504344 of the release branch
- 17 July 2013: The release branch is created at revision 1504342
- 28 June 2013: Alpha is available at revision 1497749
- 24 March 2013: Trunk is open at revision 1460483
Issues
Features and improvements | http://s.apache.org/qpid-0.24-improvements![]() |
Open bugs | http://s.apache.org/qpid-0.24-open-bugs![]() |
Fixed bugs | http://s.apache.org/qpid-0.24-fixed-bugs![]() |
Distributions
Links
Release branch | https://svn.apache.org/repos/asf/qpid/branches/0.24/![]() |
Release tag | https://svn.apache.org/repos/asf/qpid/tags/0.24/ |
Release jira | https://issues.apache.org/jira/browse/QPID-4961![]() |
Alpha test output | http://people.apache.org/~jross/qpid-0.24-alpha-testing.txt![]() |
Beta test output | http://people.apache.org/~jross/qpid-0.24-beta-testing.txt![]() |
RC1 test output | http://people.apache.org/~jross/qpid-0.24-rc1-testing.txt![]() |
RC2 test output | http://people.apache.org/~jross/qpid-0.24-rc2-testing.txt |
RC3 test output | http://people.apache.org/~jross/qpid-0.24-rc3-testing.txt |
RC4 test output | http://people.apache.org/~jross/qpid-0.24-rc4-testing.txt |
Release vote result | http://qpid.2158936.n2.nabble.com/RESULT-VOTE-Release-Qpid-0-24-td7597934.html |
Announce mail | http://qpid.2158936.n2.nabble.com/ANNOUNCE-Apache-Qpid-0-24-released-td7597972.html |
Criteria for accepting changes
- 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
19 June
- 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
3 July, 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
17 July 31 July, 2 weeks later
- RC1
- Documentation is staged for release
- Preliminary release notes are available for comment
24 July 7 August, 1 week later
- RC2
31 July 14 August, 1 week later
- RC3
- Targeted release date