Here is the proposed release schedule for OpenStack 2024.1 "Caracal". This is a 26-week cycle with a final release date on April 3, 2024. It has a longer milestone-2 period to accomodate Thanksgiving and end-of-year holidays. Also fix an issue in Bobcat release schedule where Antelope cycle-trailing deliverables were mentioned as Bobcat cycle-trailing deliverables. Change-Id: I0fb0e61e79e7e4c51d42cabd7c05bb15a05275fa
7.3 KiB
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.
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. The old phases were used until Newton.
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.
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.
- 2016-08-03..2016-11-22 (Newton Cycle key): key 0x80fcce3dc49bd7836fc2464664dbb05acc5e7c28
- 2016-11-22..2017-03-24 (Ocata Cycle key): key 0xd47bab1b7dc2e262a4f6171e8b1b03fd54e2ac07
- 2017-03-24..2017-09-15 (Pike Cycle key): key 0xc96bfb160752606daa0de2fa05eb5792c876df9a
- 2017-09-15..2018-03-19 (Queens Cycle key): key 0x4c8b8b5a694f612544b3b4bac52f01a3fbdb9949
- 2018-03-19..2018-09-05 (Rocky Cycle key): key 0xc31292066be772022438222c184fd3e1edf21a78
- 2018-09-05..2019-06-11 (Stein Cycle key): key 0x27023b1ffccd8e3ae9a5ce95d943d5d270273ada
- 2019-06-11..2019-10-29 (Train Cycle key): key 0xcdc08088c3cb45a9be08332b2354069e5b504663
- 2019-10-29..2020-05-21 (Ussuri Cycle key): key 0xbba3b1e67a7303dd1769d34595bf2e4d09004514
- 2020-05-21..2020-10-30 (Victoria Cycle key): key 0x2426b928085a020d8a90d0d879ab7008d0896c8a
- 2020-10-30..2021-05-06 (Wallaby Cycle key): key 0x5d2d1e4fb8d38e6af76c50d53d4fec30cf5ce3da
- 2021-05-06..2021-10-27 (Xena Cycle key): key 0x4c29ff0e437f3351fd82bdf47c5a3bc787dc7035
- 2021-10-27..2022-04-09 (Yoga Cycle key): key 0x01527a34f0d0080f8a5db8d6eb6c5df21b4b6363
- 2022-04-09..2022-10-07 (Zed Cycle key): key 0xa63ea142678138d1bb15f2e303bdfd64dd164087
- 2022-10-07..2023-03-31 (2023.1/Antelope Cycle key): key 0xa7475c5f2122fec3f90343223fe3bf5aad1080e4
- 2023-03-31..present (2023.2/Bobcat Cycle key): key 0x815AFEC729392386480E076DCC0DFE2D21C023C9
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