Előd Illés c48a75fb90 Add note for Extended Maintenance

Extended Maintenance does not mean by default that every project is
maintained. It could happen that a project is not actively maintained
or unmaintained or even it's team marked it as End of Life. This patch
adds a note to clarify that.

Also reformat a previous note.

Change-Id: Ib96cefe0645de1201fa06e9150a771d8ab94d2f9

2020-06-03 11:42:10 +02:00

6.3 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.

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 or End of Life on that branch. Please check specific project about its actual status on the given branch.

Series-Independent Releases

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

independent

Teams

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 Infrastructure team. 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.)

OpenStack Infrastructure root sysadmins and Release Managers publish their own signatures of these keys into the global keyserver network. 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 (details)
2016-11-22..2017-03-24 (Ocata Cycle key): key 0xd47bab1b7dc2e262a4f6171e8b1b03fd54e2ac07 (details)
2017-03-24..2017-09-15 (Pike Cycle key): key 0xc96bfb160752606daa0de2fa05eb5792c876df9a (details)
2017-09-15..2018-03-19 (Queens Cycle key): key 0x4c8b8b5a694f612544b3b4bac52f01a3fbdb9949 (details)
2018-03-19..2018-09-05 (Rocky Cycle key): key 0xc31292066be772022438222c184fd3e1edf21a78 (details)
2018-09-05..2019-06-11 (Stein Cycle key): key 0x27023b1ffccd8e3ae9a5ce95d943d5d270273ada (details)
2019-06-11..2019-10-29 (Train Cycle key): key 0xcdc08088c3cb45a9be08332b2354069e5b504663 (details)
2019-10-29..2020-05-21 (Ussuri Cycle key): key 0xbba3b1e67a7303dd1769d34595bf2e4d09004514 (details)
2020-05-21..present (Victoria Cycle key): key 0x2426b928085a020d8a90d0d879ab7008d0896c8a (details)

References

reference/using reference/release_models reference/deliverable_types reference/reviewer_guide reference/process

6.3 KiB Raw Blame History