Previous: 0.30 Release

Status

Issues

Distributions

Alphahttps://dist.apache.org/repos/dist/dev/qpid/0.32-alpha/
Betahttps://dist.apache.org/repos/dist/dev/qpid/0.32-beta/
RChttps://dist.apache.org/repos/dist/dev/qpid/0.32-rc/
RC 2

https://dist.apache.org/repos/dist/dev/qpid/0.32-rc2/

GAhttps://dist.apache.org/repos/dist/release/qpid/0.32/

Maven staging repos

RChttps://repository.apache.org/content/repositories/orgapacheqpid-1027
RC 2https://repository.apache.org/content/repositories/orgapacheqpid-1028

Links

Release branchhttps://svn.apache.org/repos/asf/qpid/branches/0.32/
Release taghttps://svn.apache.org/repos/asf/qpid/tags/0.32/
Release jirahttps://issues.apache.org/jira/browse/QPID-6359
Alpha test outputhttp://people.apache.org/~jross/qpid-0.32-alpha.log
Beta test outputhttp://people.apache.org/~jross/qpid-0.32-beta.log
RC test outputhttp://people.apache.org/~jross/qpid-0.32-rc.log
List thread that resulted in the 0.32 planhttp://qpid.2158936.n2.nabble.com/Any-ETA-on-a-QPid-0-32-release-tp7617054.html
Alpha list threadhttp://qpid.2158936.n2.nabble.com/Fwd-0-32-release-update-Alpha-is-available-td7619487.html
Beta list threadhttp://qpid.2158936.n2.nabble.com/0-32-release-update-Beta-is-available-tc7620610.html
RC list threadhttp://qpid.2158936.n2.nabble.com/0-32-release-update-RC-is-available-td7621750.html
RC 2 list threadhttp://qpid.2158936.n2.nabble.com/0-32-release-update-RC-2-is-available-td7621869.html
Release vote threadhttp://qpid.2158936.n2.nabble.com/VOTE-Release-Qpid-0-32-td7621968.html
Vote resulthttp://qpid.2158936.n2.nabble.com/RESULT-VOTE-Release-Qpid-0-32-td7622240.html
Unresolved issues list threadhttp://qpid.2158936.n2.nabble.com/0-32-unresolved-issues-td7621008.html
Release content preview list threadhttp://qpid.2158936.n2.nabble.com/0-32-release-content-preview-td7621016.html
Announce mailhttp://qpid.2158936.n2.nabble.com/ANNOUNCE-Apache-Qpid-0-32-released-td7622313.html

Change approval process

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

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 get it in the next release) and safe (not liable to cause disruption or instability).

Change acceptance criteria

Schedule

Alpha: 28 January 2015


Beta: 18 February 2015 11 February 2015, 2 weeks later


RC: 4 March 2015 25 February 2015, 2 weeks later


Additional alphas, betas, or RCs may be inserted as needed.

 More information