Page History

Previous: Qpid Proton 0.12.0

Next: 

Status

• 1 May 2016 - Alpha is available at revision 375c3edc
• 1 May 2016 - Schedule revised after two week delay

Issues

Distributions

• Alpha

Maven staging repos

Links

• Release JIRA
• Alpha test output

Change approval process

Changes to the release branch require approval. The approval has two parts:

...

• 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 - 13 April 1 May 2016

• 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 - 20 April 13 May 2016, 1 week 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 - 27 April 20 May 2016, 1 week later

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

...