Qpid Proton 0.11.0

Next: Qpid Proton 0.12.0

Status

• 19 November 2015 - The release is complete
• 16 November 2015 - The release is approved by vote
• 11 November 2015 - RC 2 is available at tag 0.11.0-rc2
• 3 November 2015 - RC is available at tag 0.11.0-rc
• 27 October 2015 - Beta is available at tag 0.11.0-beta
• 17 October 2015 - Alpha is available at revision 52dd42d8

Issues

• Features and improvements
• Open bugs
• Fixed bugs

Distributions

• Alpha
• Beta
• RC
• RC 2
• GA

Maven staging repos

• Beta
• RC
• RC 2

Links

• Release JIRA
• Release branch
• Alpha test output
• Alpha list thread
• Beta test output
• Beta list thread
• RC list thread
• RC test output
• RC 2 test output
• List discussion preceding the alpha release
• Unresolved issues thread
• Release notes and docs preview thread
• Vote thread
• Vote result thread
• Announce mail

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 - 19 October 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 - 26 October 2015, 1 week 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 - 2 November 2015, 1 week later

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