openstack/neutron
Code Issues Proposed changes

[doc] Update the release doc to create a new database branch

Browse Source 
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
This commit is contained in:
Rodolfo Alonso Hernandez 2025-03-19 09:12:26 +00:00 committed by Rodolfo Alonso
parent c9915efa0e
commit 2071dbe6eb
1 changed files with 12 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
doc/source/contributor/policies/release-checklist.rst
View File

@ -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 The following technical steps should be taken before the final release is cut
off: off:
#. the latest alembic scripts are tagged with a milestone label. For example, #. the latest alembic script of the version that is being released is tagged
see: https://review.opendev.org/c/openstack/neutron/+/755285/ 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: 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 Note that some of those steps are covered by the OpenStack release team and its
release bot. 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 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 worth keeping the infrastructure clean. Consider using these tools to declutter
the project infrastructure: the project infrastructure: