![Matthew Thode](/assets/img/avatar_default.png)
Point to the dependency management docs for general review guidelines and add docs for the freeze process. Story: 2003792 Task: 26500 Depends-On: https://review.openstack.org/615388 Change-Id: I5adb28faaeb19735445450c26bcf40ecd5336a9f
33 lines
890 B
ReStructuredText
33 lines
890 B
ReStructuredText
========================
|
|
Openstack Freeze Process
|
|
========================
|
|
|
|
PTL Actions
|
|
===========
|
|
|
|
Notice
|
|
++++++
|
|
|
|
- Email the developer mailing list approximately two weeks before the freeze.
|
|
This email should contain a notice that requirements will branch and
|
|
cycle-trailing projects should be careful if they have not branched. The
|
|
cycle-trailing projects can retarget their constraints usage to the stable
|
|
branch.
|
|
|
|
Branch
|
|
++++++
|
|
|
|
- File a review in ``openstack/releases`` with -W and only remove the -W when
|
|
ready to branch.
|
|
|
|
- Once branched, change the publish location to the new release branch.
|
|
|
|
- Once branched, update devstack grenade for the new release. For example,
|
|
use https://review.openstack.org/#/c/493057/13/devstack-vm-gate-wrap.sh
|
|
|
|
Potential issues
|
|
++++++++++++++++
|
|
|
|
- Use something like https://review.openstack.org/#/c/492382 to find problem
|
|
projects.
|