Previous: 0.28 Release

Next: 0.32 Release

Status

  • 26 September 2014: Qpid 0.30 GA is announced
  • 23 September 2014: All components are approved by vote for release; the GA artifacts are available
  • 19 September 2014: RC 2 is available
  • 11 September 2014: RC is available
  • 28 August 2014: Beta 2 is available
  • 12 August 2014: Beta is available from revision 1617305 of the release branch
  • 7 August 2014: The release branch is created at revision 1616583
  • 21 July 2014: Alpha is available from revision 1612322 of trunk
  • 20 March 2014: Trunk is open at revision 1579686

Issues

Features and improvementshttp://s.apache.org/qpid-0.30-improvements
Open bugshttp://s.apache.org/qpid-0.30-open-bugs
Fixed bugshttp://s.apache.org/qpid-0.30-fixed-bugs

 

Distributions

Alphahttps://dist.apache.org/repos/dist/dev/qpid/0.30-alpha/
Betahttps://dist.apache.org/repos/dist/dev/qpid/0.30-beta/
Beta 2https://dist.apache.org/repos/dist/dev/qpid/0.30-beta2/
RChttps://dist.apache.org/repos/dist/dev/qpid/0.30-rc/
RC 2 (for a subset of components)https://dist.apache.org/repos/dist/dev/qpid/0.30-rc2/
GAhttps://dist.apache.org/repos/dist/release/qpid/0.30/

 

Maven staging repos

Betahttps://repository.apache.org/content/repositories/orgapacheqpid-1008/, https://repository.apache.org/content/repositories/orgapacheqpid-1009/
Beta 2https://repository.apache.org/content/repositories/orgapacheqpid-1010, https://repository.apache.org/content/repositories/orgapacheqpid-1011
RChttps://repository.apache.org/content/repositories/orgapacheqpid-1012

 

Release branchhttps://svn.apache.org/repos/asf/qpid/branches/0.30/
Release taghttps://svn.apache.org/repos/asf/qpid/tags/0.30/
Release JIRA Unable to locate Jira server for this macro. It may be due to Application Link configuration.
Alpha test output

http://people.apache.org/~jross/qpid-trunk-2014-07-21.log

Alpha maven artifactshttp://people.apache.org/~jross/maven-trunk-2014-07-21/
Alpha list threadhttp://qpid.2158936.n2.nabble.com/0-30-release-update-alpha-is-available-tt7610692.html
Beta test outputhttp://people.apache.org/~jross/qpid-0.30-beta.log
Beta list threadhttp://qpid.2158936.n2.nabble.com/0-30-release-update-beta-is-available-tt7611678.html
Beta 2 list threadhttp://qpid.2158936.n2.nabble.com/0-30-release-update-Beta-2-is-available-td7612764.html
RC test outputhttp://people.apache.org/~jross/qpid-0.30-rc.log
RC list threadhttp://qpid.2158936.n2.nabble.com/0-30-release-update-Release-candidate-td7613524.html
Release vote threadhttp://qpid.2158936.n2.nabble.com/VOTE-Release-Qpid-0-30-components-td7613719.html
RC 2 vote threadhttp://qpid.2158936.n2.nabble.com/VOTE-Release-revised-0-30-python-qmf-tests-and-tools-components-td7613887.html
RC Vote resulthttp://qpid.2158936.n2.nabble.com/RESULT-VOTE-Release-Qpid-0-30-components-td7614040.html
RC 2 vote resulthttp://qpid.2158936.n2.nabble.com/RESULT-VOTE-Release-revised-0-30-python-qmf-tests-and-tools-components-td7614041.html
Announce mailhttp://qpid.2158936.n2.nabble.com/ANNOUNCE-Apache-Qpid-0-30-released-td7614337.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 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

Schedule

Alpha: 21 July 2014 16 July 2014

  • 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: 12 August 2014 30 July 2014, 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

Beta 2: 27 August 2014, 2 weeks later


RC: 10 September 2014, 2 weeks later 13 August 2014, 2 weeks later


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

  • No labels