Previous: 0.30 Release


  • 20 March 2015: Qpid 0.32 GA is announced
  • 19 March 2015: All components are approved by vote for release; the GA artifacts are available
  • 12 March 2015: RC 2 is available from revision 1666029 of the release branch
  • 10 March 2015: RC is available from revision 1665516 of the release branch
  • 19 February 2015: Beta is available from revision 1660917 of the release branch
  • 19 February 2015: The release branch is created at revision 1660913
  • 3 February 2015: Alpha is available from revision 1656805 of trunk
  • 7 August 2014: Trunk is open at revision 1616583



Maven staging repos

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 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 RC: Bug fixes only; exceptions are sometimes made for improvements that are important, isolated, and small in terms of code delta

  • After RC: Bug fixes for important defects only, such as build failures, regressions, or security vulnerabilities


Alpha: 28 January 2015

  • 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: 18 February 2015 11 February 2015, 2 weeks later

  • The release branch is created
  • Release branch commits require approval
  • Release manager produces outstanding bug report
  • Trunk opens for development toward the next release
  • Preliminary release notes and documentation are available for review

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

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

 More information

  • No labels