You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Previous: 0.28 Release

Next: 0.32 Release

Status

  • 21 July 2014: Alpha is available from revision 1612322 of trunk
  • 20 March 2014: Trunk is open at revision 1579686

Issues

None

Distributions

Alphahttps://dist.apache.org/repos/dist/dev/qpid/0.30-alpha/

 

Release JIRA Unable to render Jira issues macro, execution error.
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/

 

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: 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: 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


RC: 13 August 2014, 2 weeks later

  • Preliminary release notes and documentation are available for review


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

  • No labels