openstack/releases
Code Issues Proposed changes
releases/doc/source/index.rst
Clark Boylan 026fc0186e Render a graph showing the SLURP and not SLURP upgrade paths 
I think visual representation can help people understand the practical
effects of the SLURP releases on their upgrade options. Lets add one
using graphviz to do the rendering for us.

Change-Id: Ic28c8ad4bc84f094a37b38037a6859d725e85f51
2024-10-02 14:49:21 +00:00

8.9 KiB
Raw Blame History

OpenStack Releases

Release Series

OpenStack is developed and released around 6-month cycles. After the initial release, additional stable point releases will be released in each release series. You can find the detail of the various release series here on their series page. Subscribe to the combined release calendar for continual updates.

epoxy/index dalmatian/index caracal/index bobcat/index antelope/index zed/index yoga/index xena/index wallaby/index victoria/index ussuri/index train/index stein/index rocky/index queens/index pike/index ocata/index newton/index mitaka/index liberty/index kilo/index juno/index icehouse/index havana/index grizzly/index folsom/index essex/index diablo/index cactus/index bexar/index austin/index releases/*

Note

The schedule of Maintenance phases changed during Ocata and also during 2024.1 Caracal. The old phases were used until Newton. The last series that transitioned to Extended Maintenance was Xena. The replacement of Extended Maintenance process to Unmaintained was formulated in the 2023-07-24 Unmaintained status replaces Extended Maintenance resolution.

Note

If a branch is marked as Extended Maintenance, that means individual projects can be in state Maintained, Unmaintained, Last or End of Life on that branch. Please check specific project about its actual status on the given branch.

Series-Independent Releases

Some deliverables are released independently from the OpenStack release series. You can find their releases listed here:

independent

Releases with Skip Level Upgrade Release Process (SLURP)

Releases can be marked as Skip Level Upgrade Release Process (or SLURP) releases. This practically means, that upgrades will be supported between these (SLURP) releases, in addition to between adjacent major releases. For example the upgrade paths starting with the 2023.1 Antelope release look like this:

digraph openstack_releases {

label="OpenStack Upgrade Paths" splines=false; nodesep=1; rankdir="LR"; node [shape=box];

A [label="2023.1nAntelope"]; C [label="2024.1nCaracal"]; B [label="2023.2nBobcat"]; E [label="2025.1nEpoxy"]; D [label="2024.2nDalmatian"];

A -> C [xlabel="SLURP"]; A -> B; B -> C;

C -> E [xlabel="SLURP"]; C -> D; D -> E;

}

Teams

Deliverables are produced by project teams. Here you can find all OpenStack deliverables, organized by the team that produces them:

teams/*

Cryptographic Signatures

Git tags created through our release automation are signed by centrally-managed OpenPGP keys maintained by the OpenStack TaCT SIG. Detached signatures of many separate release artifacts are also provided using the same keys. A new key is created corresponding to each development cycle and rotated relatively early in the cycle. (Implementation completed late in the Newton cycle, so many early Newton artifacts have no corresponding signatures.) Copies of the public keys can be found below along with the date ranges during which each key was in general use.

Documentation

Content for this site is automatically generated from the data submitted to the openstack/releases git repository. You can learn more about this repository and the release management team processes in the following documentation:

reference/using reference/release_models reference/deliverable_types reference/join_release_team reference/reviewer_guide reference/release_infra reference/process