From c52e685e5f5e9ad3493b0e0ad5d755c3304e358b Mon Sep 17 00:00:00 2001 From: Iury Gregory Melo Ferreira Date: Fri, 24 Sep 2021 11:04:24 +0200 Subject: [PATCH] Update release doc - move ipa-builder to projects that follow normal release - add a new section Manual release for ironic-staging-driver - update Things to do after releasing. Change-Id: Ie6d02096dc15fc8c3f881556f1638d94ba2d8ece --- doc/source/contributor/releasing.rst | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/doc/source/contributor/releasing.rst b/doc/source/contributor/releasing.rst index 6b1d49b3c6..a3084a0f9c 100644 --- a/doc/source/contributor/releasing.rst +++ b/doc/source/contributor/releasing.rst @@ -78,6 +78,10 @@ The following deliverables are Tempest plugins: * ironic-tempest-plugin +The following deliverables are tools: + +* ironic-python-agent-builder + The following deliverables are services, or treated as such: * bifrost @@ -86,13 +90,19 @@ The following deliverables are services, or treated as such: * ironic-prometheus-exporter * ironic-python-agent +Manual release +-------------- + +The ironic-staging-drivers follows a different procedure, see +`Releasing ironic-staging-drivers +`__. + Independent ----------- The following deliverables are released `independently `__: -* ironic-python-agent-builder * sushy-tools * tenks * virtualbmc @@ -293,10 +303,6 @@ We need to submit patches for changes in the stable branch to: * update the ironic devstack plugin to point at the branched tarball for IPA. An example of this patch is `here `_. -* update links in the documentation (``ironic/doc/source/``) to point to the - branched versions of any openstack projects' (that branch) documents. - As of Pike release, the only outlier is - `diskimage-builder `_. * set appropriate defaults for ``TEMPEST_BAREMETAL_MIN_MICROVERSION`` and ``TEMPEST_BAREMETAL_MAX_MICROVERSION`` in ``devstack/lib/ironic`` to make sure that unsupported API tempest tests are skipped on stable branches. E.g. @@ -304,12 +310,6 @@ We need to submit patches for changes in the stable branch to: We need to submit patches for changes on master to: -* create an empty commit with a ``Sem-Ver`` tag to bump the generated minor - version. See `example - `_ - and `pbr documentation - `_ for details. - * 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