Release candidate Freeze (RF)
ReleaseCandidateFreeze (RF) is one of the milestones in OpenStack's release schedule. Like all freezes, it happens at the end of the day (or 23:59 PST).
Freeze
Once RF kicks in, you are no longer allowed to merge any branch.
Rationale
RF allows to build a release candidate that is very likely to be the final release. Only extremely critical issues will be considered important enough to justify an emergency respin of the release deliverables.
RF occurs two days before release.
Exception procedure
If you want to propose or merge a branch containing a critical bugfix for merging into the development release after RF, follow those steps:
- If there is no bug opened about the issue in Launchpad yet, please open one
- Link the bug to your bugfix branch
- Propose your branch for merging
- In a specific comment on the merge proposal, provide the following information:
- Benefit of the branch
- Risk of regression
- In the merge proposal, "Request a review" from the Release Manager and set review type to "RFE"
The Release manager will evaluate the request and grant or deny the exception. Exceptions of this nature should be extremely rare.