Status
18 February 2014: Qpid 0.26 is generally available
8 February 2014: The vote to release RC4 as final is approved
2 February 2014: Proposed final RC4 is available at revision 1563358 of the release branch
16 January 2014: RC3 is available at revision 1558617 of the release branch
23 December 2013: RC2 is available at revision 1551622 of the release branch
- 1 December 2013: RC1 is available at revision 1545843 of the release branch
- 13 November 2013: Beta is available at revision 1541291 of the release branch
- 12 November 2013: The release branch is created at revision 1541273
- 24 October 2013: Alpha is available at revision 1535277 of trunk
- 17 July 2013: Trunk is open at revision 1504342
Issues
Features and improvements | http://s.apache.org/qpid-0.26-improvements![]() |
Open bugs | http://s.apache.org/qpid-0.26-open-bugs![]() |
Fixed bugs | http://s.apache.org/qpid-0.26-fixed-bugs![]() |
Distributions
Links
Release branch | https://svn.apache.org/repos/asf/qpid/branches/0.26/![]() | |
Release tag | https://svn.apache.org/repos/asf/qpid/tags/0.26/ | |
Release jira | https://issues.apache.org/jira/browse/QPID-5255![]() | |
Alpha test output | http://people.apache.org/~jross/qpid-0.26-alpha-testing.txt![]() | |
Beta test output | http://people.apache.org/~jross/qpid-0.26-beta-testing.txt | |
RC1 test output | http://people.apache.org/~jross/qpid-0.26-rc1-testing.txt | |
RC2 test output | http://people.apache.org/~jross/qpid-0.26-rc2-testing.txt | |
RC3 test output | http://people.apache.org/~jross/qpid-0.26-rc3-testing.txt | |
RC4 test output | http://people.apache.org/~jross/qpid- | testing.txt0.26-rc4-testing.txt |
Release vote result | http://qpid.2158936.n2.nabble.com/RESULT-VOTE-Release-Qpid-0-26-td7604220.html | |
Announce mail | http://qpid.2158936.n2.nabble.com/ANNOUNCE-Apache-Qpid-0-26-released-td7604531.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
...
- vulnerabilities
Schedule
16 October
- 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
30 October 6 November, 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 November 20 November 1 December, 2 weeks later
- RC1
- Documentation is staged for release
- Preliminary release notes are available for comment
20 November 27 November 11 December, 1 week later
- RC2
27 November 4 December, 1 week later 8 January
- RC3
- Targeted release date