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

Compare with Current View Page History

« Previous Version 7 Next »

Previous: 0.26
Next: 0.30

Status

  • 5 March 2013: Alpha is available at revision 1574236 of trunk
  • 12 November 2013: Trunk is open at revision 1541273

Issues

Features and improvements

 

Open bugs

 

Fixed bugs

 

Distributions

Alphahttps://dist.apache.org/repos/dist/dev/qpid/0.28-alpha/
Release jira Unable to locate Jira server for this macro. It may be due to Application Link configuration.
Alpha maven artifacts

http://people.apache.org/~jross/maven-0.28-alpha/

Alpha test outputhttp://people.apache.org/~jross/qpid-0.28-alpha-testing.txt

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

RC1: 12 March 26 March, 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, 1 week later

RC3: 26 March 9 April, 1 week later

  • Targeted release date
  • No labels