[all][tc] Change OpenStack release naming policy proposal

Slawek Kaplonski skaplons at redhat.com
Fri Apr 29 14:55:52 UTC 2022


During the last PTG in April 2022 in the TC meeting we were discussing our release naming policy [1].
It seems that choosing appropriate name for every releases is very hard and time consuming. There is many factors which needs to be taken into consideration there like legal but also meaning of the chosen name in many different languages.

Finally we decided that now, after Zed release, when we will go all round through alphabet it is very good time to change this policy and use only numeric version with "year"."release in the year". It is proposed in [2].
This is also good timing for such change because in the same release we are going to start our "Tick Tock" release cadence which means that every Tick release will be release with .1 (like 2023.1, 2024.1, etc.) and every Tock release will be one with .2 (2023.2, 2024.2, etc.).

[1] https://etherpad.opendev.org/p/tc-zed-ptg#L265[1]
[2] https://review.opendev.org/c/openstack/governance/+/839897[2]

Slawek Kaplonski
Principal Software Engineer
Red Hat

[1] https://etherpad.opendev.org/p/tc-zed-ptg#L265
[2] https://review.opendev.org/c/openstack/governance/+/839897
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20220429/175b0fbc/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20220429/175b0fbc/attachment.sig>

More information about the openstack-discuss mailing list