openstack/releases
Code Issues Proposed changes

Add instructions for linking a requirements update to release request

Browse Source 
Change-Id: I41a4bd707083e41589e6bc92ccac6ceb4197aa91
This commit is contained in:
Doug Hellmann 2015-09-25 18:43:02 +00:00
parent 7f5b643632
commit 1b16f9b749
1 changed files with 25 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
doc/source/instructions.rst
View File

@ -20,6 +20,21 @@ the stable release is requested by the stable maintenance team, it
should be acknowledged by the PTL or release liaison to ensure that should be acknowledged by the PTL or release liaison to ensure that
the development team is aware of the coming change. the development team is aware of the coming change.
#. Prepare the release request by submitting a patch to this
repository.
#. Prepare an update to the openstack/requirements repository to
change upper-constraints.txt to ensure the new release is tested in
the gate. You may also need to update global-requirements.txt in
the same patch for a release with new features on which a project
depends (bug fix releases do not need the requirements
updated). Use a ``Depends-On`` tag in the commit message to tie the
patch to the original release request so that the requirements and
constraints patch will not merge until the release request merges.
#. Leave a comment on the release request linking it to the
requirements repository update.
Reviewing a Release Request Reviewing a Release Request
--------------------------- ---------------------------
@ -45,6 +60,16 @@ General notes when reviewing a release request:
`stable-maint-core <https://review.openstack.org/#/admin/groups/530,members>`_ `stable-maint-core <https://review.openstack.org/#/admin/groups/530,members>`_
team should +1 a change like this before it's approved. team should +1 a change like this before it's approved.
* Make sure there is a requirements update patch to enable use of the
new release. With the constraints system in place, releasing a
library is no longer sufficient to cause it to be used in the CI
systems. We must explicitly update the constraints file for
integration tests, and we want to ensure that the lower bounds
accurately reflect the versions needed to provide features for the
consuming applications. This latter step is difficult to do
accurately via a script, so we need it to be done by the person
releasing the library.
The following rules apply mostly to stable branches and therefore a member of The following rules apply mostly to stable branches and therefore a member of
the `stable-maint-core <https://review.openstack.org/#/admin/groups/530,members>`_ the `stable-maint-core <https://review.openstack.org/#/admin/groups/530,members>`_
team should +1 the following types of changes before they are approved. team should +1 the following types of changes before they are approved.