openstack/releases
Code Issues Proposed changes

Merge "add a step to submit the devstack patch to set the default branch"

Browse Source
This commit is contained in:
Jenkins 2017-08-11 23:33:58 +00:00 committed by Gerrit Code Review
commit 8fe2d5e85f
1 changed files with 11 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
PROCESS.rst
View File

@ -205,13 +205,16 @@ RC1
devstack branch can be created. Devstack doesn't push a tag at RC1 it is
just branched off of HEAD
3. After devstack is branched a grenade branch can be created. As with devstack
it will branch from HEAD instead of a tag.
3. After devstack is branched a grenade branch can be created. As with
devstack it will branch from HEAD instead of a tag.
4. Update the grenade settings in devstack-gate for the new branch. For
4. Update the default branch for devstack in the new stable
branch. For example, https://review.openstack.org/#/c/493208/
5. Update the grenade settings in devstack-gate for the new branch. For
example, https://review.openstack.org/362438.
5. For translations, create stable-$series versions in the Zanata
6. For translations, create stable-$series versions in the Zanata
translation server on https://translate.openstack.org for all
projects that the translation team wants to handle. Create new
translation-jobs-$series periodic jobs to import translations from
@ -220,7 +223,7 @@ RC1
Note this work is done by translation team.
6. After all cycle-with-milestone projects have their branches
7. After all cycle-with-milestone projects have their branches
created, update the deliverable file to create the stable/$series
branch for ``openstack/requirements``. Then announce that the
requirements freeze is lifted from master.
@ -234,17 +237,17 @@ RC1
and we can have divergence between the requirements being tested
and being declared as correct.
7. Create new branch specific jobs for our two branchless projects,
8. Create new branch specific jobs for our two branchless projects,
devstack-gate and tempest, and configure Zuul to run them on all
changes to those projects to protect against regressions with the
stable branches and these tools. For example, see
https://review.openstack.org/375110.
8. Create periodic bitrot jobs for the new branch in Jenkins Job
9. Create periodic bitrot jobs for the new branch in Jenkins Job
Builder and add them to Zuul's periodic pipeline. For example, see
https://review.openstack.org/#/c/375092.
9. Add periodic bitrot jobs to tempest. For example, see
10. Add periodic bitrot jobs to tempest. For example, see
https://review.openstack.org/#/c/375271.
Between RC1 and Final