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

Compare with Current View Page History

Version 1 Next »

Previous: Qpid Proton 0.13.0

Next: 

Status

  • 1 August 2016 - The 0.14.x release branch is created

Issues

Distributions

Maven staging repos

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

 

 

  • No labels