[all][tc] Change OpenStack release naming policy proposal
Thomas Goirand
zigo at debian.org
Fri Apr 29 15:54:34 UTC 2022
As someone that can tell by heart all of the 26 release names, I will
wholeheartedly regret release names.
Is the decision final, or can it still be reverted?
Cheers,
Thomas Goirand (zigo)
On 4/29/22 16:55, Slawek Kaplonski 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
> <https://etherpad.opendev.org/p/tc-zed-ptg#L265>
>
> [2] https://review.opendev.org/c/openstack/governance/+/839897
> <https://review.opendev.org/c/openstack/governance/+/839897>
>
>
> --
>
> Slawek Kaplonski
>
> Principal Software Engineer
>
> Red Hat
>
More information about the openstack-discuss
mailing list