openstack/releases
Code Issues Proposed changes

document another reason to force tags on intermediary projects

Browse Source 
Change-Id: I14d9d32b5191a4f90dfe357143d5a2214d13b36b
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
This commit is contained in:
Doug Hellmann 2018-07-20 11:34:47 -04:00
parent 6e87818046
commit 96cd9848f0
1 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/source/reference/process.rst
View File

@ -153,7 +153,13 @@ Final Library Release (week before Milestone-3)
changes merged over the cycle but no release yet. Do not create
branches for non-library projects.
6. For stable libraries that did not have any change merged over the
6. Tag HEAD of master for any cycle-with-intermediary project that has
unreleased CI configuration changes that would not have triggered a
release earlier in the cycle. Failing to tag means those CI changes
will not be on the stable branch and so the stable branch may start
out broken. Do not create branches for non-library projects.
7. For stable libraries that did not have any change merged over the
cycle, create a stable branch from the last available release.