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.

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 OpenStack Technical Committee has passed a resolution for the release identification process. The release number will be used as the primary identifier in the development cycle but the release name will also be used in some places.

  • Stable branches: Use release number for stable branch name. Example: stable/2023.1

  • Spec repo or any other directory structure: Use release number which is more aligned with what stable branches are going to use.

  • Testing tools: Use release number which is more aligned with what stable branches are going to use.

  • Release page/tooling/milestone name: The release team can choose either to continue using the release name or use number for release tooling and milestone name.

Release Name

We will continue with the release name but mainly for marketing usage.

  • OpenStack release names will be handled by the staff of the OpenInfra Foundation.

  • Foundation staff will define the naming criteria and process but make sure they satisfy the OpenStack release team’s tooling requirements.

  • The OpenStack release team PTL sign-off is needed on naming criteria defined by the Foundation staff.

  • The OpenStack Technical Committee will not be involved in the process, the release team will directly coordinate with the foundation staff.

Release Name Selection History

Release

Coordinator

Nominations Open

Poll Open

Poll Close

Geographic Region

M

Monty Taylor

2015-06-01

2015-06-08

2015-06-15

Tokyo

N

Monty Taylor

2015-11-08

2015-11-30

2015-12-07

Texas Hill Country

O

Monty Taylor

2015-11-08

2015-11-30

2015-12-07

Catalonia

P

Monty Taylor

2016-06-22

2016-07-06

2016-07-13

New England

Q

Monty Taylor

2016-06-22

2016-07-06

2016-07-13

New South Wales

R

Monty Taylor

2017-03-22

2017-04-05

2017-04-12

British Columbia

S

Paul Belanger

2018-02-21

2018-03-14

2018-03-21

Berlin

T

Tony Breeds

2018-09-15

2018-10-15

2018-10-22

Colorado

U

Rico Lin

2019-07-01

2019-08-12

2019-08-19

China

V

Sean McGinnis

2019-11-11

2019-12-09

2019-12-16

British Columbia

W

Sean McGinnis

2020-01-20

2020-02-17

2020-02-23

N/A *

X

Sean McGinnis

2020-11-02

2020-11-30

2020-12-06

N/A

Y

Ghanshyam Mann

2021-05-13

2021-06-10

2021-06-17

N/A

Z

Ghanshyam Mann

2022-01-11

2022-01-25

2022-02-01

N/A

The Zed release is the last release for which the OpenStack Technical Committee was involved in the selection of the release name.

*

Starting with the W release, the naming criteria changed from referring to the physical or human geography of the region encompassing the location of the OpenStack Summit, to any name proposed by the community that starts with the designated release letter.