opendev
/
infra-manual
Code Issues Proposed changes

clarify the expected policy for managing releases 

The release team expects all official teams producing content that is
"part of the release" to use the release automation processes and have
their tags reviewed. Clarify that and redirect folks looking for
instructions about tagging to the relevant documentation.

Change-Id: Ie80f0720656bcbe1e08563344bc687166fc3ac2d
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
This commit is contained in:
Doug Hellmann 2017-05-22 10:00:58 -04:00
parent a88d483136
commit 3aa50eeaa9
1 changed files with 8 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
doc/source/drivers.rst
View File

@ -214,9 +214,14 @@ You can learn more about `stable branches in the project team guide
Tagging a Release
~~~~~~~~~~~~~~~~~
This step should be performed by the OpenStack Release Management Team
when the release is made. If you are managing your own releases, you may
have permission to do this yourself.
Deliverables produced by official teams and released following the
release cycle should be managed by the OpenStack Release Management
Team. See the instructions in the `README.rst
<http://git.openstack.org/cgit/openstack/releases/tree/README.rst>`__
in openstack/releases for details.
If you are managing your own releases, you may have permission to do
this yourself.
Tag the tip of the appropriate branch (stable/<series> for server
projects using release candidates, master for the others) with a release tag