Hervé Beraud 14484c5055 Fix propose-final-releases command to use release-id
With the new release identification / naming schema [1] (like:
2023.1 Antelope) new stable branch naming was introduced (like:
stable/2023.1). This was not handled in the propose-final-releases command as
it still uses the release name. This patch fixes this by reading the
'release-id' field from series_status.yaml and if present then uses it
as stable/<release-id> for the branch creation.

[1] https://governance.openstack.org/tc/reference/release-naming.html

Change-Id: Ie8ba3e9bfa01148e93f5920050703e998248db11
2023-03-20 11:05:56 +01:00
..
2015-07-23 17:33:03 +00:00
2022-07-26 12:24:11 +02:00
2022-04-19 10:19:15 +08:00
2022-03-16 20:30:07 +01:00
2021-03-05 17:32:09 +01:00
2020-04-27 11:23:28 -05:00
2020-04-13 11:54:40 -05:00
2023-03-03 16:48:11 +01:00