openstack/governance
Code Issues Proposed changes

Release identification and release name

Browse Source 
Since 2010, we went from 26 different OpenStack releases names
(from "A" - "Austin" to "Z" - "Zed"). It's now time to define an
unambiguous and sustainable release schema to easily identify
different OpenStack releases without taking into account the alphabet
iteration.

With this change the TC proposes to move the release identification
from only a release name (ex: "Axxxx") to "year"."release count within
the year" "release name" (ex: 2023.1 Axxxx). This will help to bring
more clarity for releases support and future feature deprecations.

The release name will continue to be used for marketing purposes and
community engagement. The same release name process and criteria will
continue to be used. When the end of the alphabet is reached we start
again from the first letter of the alphabet (after "Z", the next
name should start with "A" again).

The release number of each individual project is independent of the
release identification/name.

Change-Id: I595504a101138ee4a2afd358dc4af8f6617aa845
This commit is contained in:
Belmiro Moreira 2022-02-16 15:34:40 +00:00
parent 488915ce63
commit aaa531c75d
1 changed files with 34 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

37
reference/release-naming.rst
View File

@ -1,6 +1,34 @@
==============
Release Naming
==============
===========================
Release Identification/Name
===========================
Release Identification
----------------------
After the release "Zed", each OpenStack release has an
identification code: "year"."release count within the year"
Example:
* OpenStack 2023.1 Axxxx
Where "2023" is the year of the release, "1" represents the first release
of the year and "Axxxx" is the release name following the release name rules.
Other examples:
* OpenStack 2023.2 Bxxxx
* OpenStack 2024.1 Cxxxx
With this release identification schema we get an easy and sustainable
approach to identify different OpenStack releases without dealing with the
ambiguity of the release name and alphabet iteration.
The release identification schema doesn't replace the release name.
It's just an unambiguous way to identify OpenStack releases.
Release Name
------------
Each OpenStack development cycle has a code-name that is
proposed and chosen by the community. This name is frequently used in
@ -43,6 +71,9 @@ being chosen.
starting with the initial release of "Austin". After "Z", the next
name should start with "A" again.
#. A release name can't be repeated between different iterations of the
alphabet.
#. The name must be composed only of the 26 characters of the ISO
basic Latin alphabet. Names which can be transliterated into this
character set are also acceptable.