openstack
/
neutron
Code Issues Proposed changes

Change the release tag to use the release identification 

According to the TC resolution [1] and the release identification
document [2], the release number will be used as primary identifier in
the development cycle. Release name will be used in marketing.

[1]https://governance.openstack.org/tc/resolutions/20220524-release-identification-process.html
[2]https://governance.openstack.org/tc/reference/release-naming.html

Change-Id: Ia3da9bf6d6113edacb0e21de9a51bd60d5e2465b
This commit is contained in:
Rodolfo Alonso Hernandez 2023-03-01 19:52:52 +01:00
parent 92766c85b6
commit 39b65575cd
3 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
neutron/db/migration/__init__.py
View File

@ -37,7 +37,7 @@ WALLABY = 'wallaby'
XENA = 'xena'
YOGA = 'yoga'
ZED = 'zed'
ANTELOPE = 'antelope'
RELEASE_2023_1 = '2023.1'
NEUTRON_MILESTONES = [
# earlier milestones were not tagged
@ -55,7 +55,7 @@ NEUTRON_MILESTONES = [
WALLABY,
XENA,
YOGA,
ANTELOPE,
RELEASE_2023_1,
# Do not add the milestone until the end of the release
]

0
neutron/db/migration/alembic_migrations/versions/antelope/expand/fc153938cdc1_update_segment_networks_constraint.py → neutron/db/migration/alembic_migrations/versions/2023.1/expand/fc153938cdc1_update_segment_networks_constraint.py
View File

4
neutron/db/migration/cli.py
View File

@ -38,7 +38,7 @@ HEADS_FILENAME = 'HEADS'
CONTRACT_HEAD_FILENAME = 'CONTRACT_HEAD'
EXPAND_HEAD_FILENAME = 'EXPAND_HEAD'
CURRENT_RELEASE = migration.ANTELOPE
CURRENT_RELEASE = migration.RELEASE_2023_1
RELEASES = (
migration.LIBERTY,
migration.MITAKA,
@ -55,7 +55,7 @@ RELEASES = (
migration.XENA,
migration.YOGA,
migration.ZED,
migration.ANTELOPE,
migration.RELEASE_2023_1,
)
EXPAND_BRANCH = 'expand'