Previous: 0.26
Next: 0.30

Status

• 3 June 2014: Qpid 0.28 is generally available
• 13 May 2014: Proposed final RC2 is available at revision 1594179 of the release branch
• 24 April 2014: RC1 is available at revision 1589856 of the release branch
• 10 April 2014: Beta 2 is available at revision 1586009 of the release branch
• 20 March 2014: Beta is available at revision 1579693 of the release branch
• 20 March 2014: The release branch is created at revision 1579686
• 5 March 2014: Alpha is available at revision 1574236 of trunk
• 12 November 2013: Trunk is open at revision 1541273

Issues

Distributions

Links

Release branch	https://svn.apache.org/repos/asf/qpid/branches/0.28/
Release jira
Alpha maven artifacts	http://people.apache.org/~jross/maven-0.28-alpha/
Alpha test output	http://people.apache.org/~jross/qpid-0.28-alpha-testing.txt
Beta maven artifacts	http://people.apache.org/~jross/maven-0.28-beta/
Beta 2 maven artifacts	http://people.apache.org/~jross/maven-0.28-beta2/
Beta test output	http://people.apache.org/~jross/qpid-0.28-beta-testing.txt
Beta 2 test output	http://people.apache.org/~jross/qpid-0.28-beta2-testing.txt
RC 1 maven artifacts	http://people.apache.org/~jross/maven-0.28-rc1/
RC 2 maven artifacts	http://people.apache.org/~jross/maven-0.28-rc2/
RC 2 maven artifacts with release names	http://people.apache.org/~jross/maven-0.28-rc2-renamed-for-release/
RC 2 release output	http://people.apache.org/~jross/qpid-0.28-rc2.log
Release vote result	http://qpid.2158936.n2.nabble.com/RESULT-VOTE-Release-Qpid-0-28-td7608844.html
Announce mail	http://qpid.2158936.n2.nabble.com/ANNOUNCE-Apache-Qpid-0-28-released-td7608879.html

Change approval process

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.

Any changes requested should be consistent with the acceptance criteria listed below. In general, a change for the release branch should be important (if it's not important, we'll just wait to get it in the next release) and safe (not liable to cause disruption or instability).

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: 19 February 5 March

• 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: 5 March 19 March, 2 weeks later

• The release branch is created
• Release branch commits require approval
• Trunk opens for development toward the next release

Beta 2: 9 April

RC1: 12 March 26 March 16 April, 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

RC2: 19 March 2 April 23 April, 1 week later

RC3: 26 March 9 April 30 April, 1 week later

• Targeted release date