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

Cedric Lemarchand yipikai7 at gmail.com
Fri Apr 29 19:39:18 UTC 2022

Maybe a best of breed approach would be to have both, like Ubuntu releases.
It does not solve the time consuming and others issues regarding naming
choices but I see it as a good consensual solution at this time.

My 2 cents


On Fri, Apr 29, 2022, 16:59 Slawek Kaplonski <skaplons at redhat.com> wrote:

> Hi,
> 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
> [2] https://review.opendev.org/c/openstack/governance/+/839897
> --
> Slawek Kaplonski
> Principal Software Engineer
> Red Hat
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20220429/0d79ef65/attachment.htm>

More information about the openstack-discuss mailing list