From 2071dbe6ebb13a2293cef0eabbcf993694f476f0 Mon Sep 17 00:00:00 2001 From: Rodolfo Alonso Hernandez Date: Wed, 19 Mar 2025 09:12:26 +0000 Subject: [PATCH] [doc] Update the release doc to create a new database branch The document includes an updated example and the checkpoints to create a new database branch when a version is released and a new master/main branch starts its cycle. Related-Bug: #2103531 Change-Id: Id0436f8e50fd18765ff6ec94406e2de7ca8c3dfd --- .../policies/release-checklist.rst | 20 +++++++++++-------- 1 file changed, 12 insertions(+), 8 deletions(-) diff --git a/doc/source/contributor/policies/release-checklist.rst b/doc/source/contributor/policies/release-checklist.rst index 58a71881257..ee5105d1e71 100644 --- a/doc/source/contributor/policies/release-checklist.rst +++ b/doc/source/contributor/policies/release-checklist.rst @@ -63,8 +63,18 @@ Release candidate (RC) process allows for stabilization of the final release. The following technical steps should be taken before the final release is cut off: -#. the latest alembic scripts are tagged with a milestone label. For example, - see: https://review.opendev.org/c/openstack/neutron/+/755285/ +#. the latest alembic script of the version that is being released is tagged + with a milestone label; for example, in + https://review.opendev.org/c/openstack/neutron/+/944804 the latest script + is being tagged with ``RELEASE_2025_1`` +#. the new release tag must be created; using the previous example, the tag + ``RELEASE_2025_2`` is created. +#. add the released version tag to the ``NEUTRON_MILESTONES`` list; in the + previous example, the tag ``RELEASE_2025_1`` is added to this list. +#. update the ``CURRENT_RELEASE`` variable with the new tag created and + add it to the ``RELEASES`` tuple; in the previous example, + ``RELEASE_2025_2`` is added to the ``RELEASES`` tuple and used as the + current release milestone. In the new stable branch, you should make sure that: @@ -99,12 +109,6 @@ In the new stable branch, you should make sure that: Note that some of those steps are covered by the OpenStack release team and its release bot. - -In the opened master branch, you should: - -#. update CURRENT_RELEASE in neutron.db.migration.cli to point to the next - release name. - While preparing the next release and even in the middle of development, it's worth keeping the infrastructure clean. Consider using these tools to declutter the project infrastructure: