summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorRuby Loo <ruby.loo@intel.com>2018-02-20 11:42:36 -0500
committerRuby Loo <ruby.loo@intel.com>2018-02-20 11:42:36 -0500
commit85581f3bb9a9fa1eb7d0c6a83dba3f1059762e0e (patch)
treefdf08654c36b2fbab83bf930a73fca70c76ca672 /doc
parentccc251cadb0c9f75e6b47cbd46166bcec7632ffa (diff)
downloadironic-85581f3bb9a9fa1eb7d0c6a83dba3f1059762e0e.tar.gz
Update release instructions wrt grenade
This updates the release documentation to indicate that we have to wait until grenade is testing the latest release against master, before making code changes related to rolling upgrades. Change-Id: I60a3343cfb4565da725a7b39c6ee8b04e4389dec
Diffstat (limited to 'doc')
-rw-r--r--doc/source/contributor/releasing.rst9
1 files changed, 8 insertions, 1 deletions
diff --git a/doc/source/contributor/releasing.rst b/doc/source/contributor/releasing.rst
index 7ee994554..33c7c3d33 100644
--- a/doc/source/contributor/releasing.rst
+++ b/doc/source/contributor/releasing.rst
@@ -108,7 +108,14 @@ We need to submit patches for changes on master to:
and `pbr documentation
<https://docs.openstack.org/pbr/latest/user/features.html#version>`_ for details.
-* to support rolling upgrades, since the release was a named release:
+* to support rolling upgrades, since the release was a named release, we
+ need to make these changes. Note that we need to wait until *after* the
+ switch in grenade is made to test the latest release (N) with master
+ (e.g. `for stable/queens <https://review.openstack.org/#/c/543615>`_).
+ Doing these changes sooner -- after the ironic release and before the switch
+ when grenade is testing the prior release (N-1) with master, will cause
+ the tests to fail. (You may want to ask/remind infra/qa team, as to
+ when they will do this switch.)
* In ``ironic/common/release_mappings.py``, delete any entries from
``RELEASE_MAPPING`` associated with the oldest named release. Since we