Files

Doug Hellmann f446ef37f4 generate the series status table from data

Move the information about the series status into a data file and use
that to generate the table on the main page. This is the first step
toward adding deliverable-specific series status information to the
output, since we need a place to put the default values.

Because we're adding a yaml file under the deliverables directory that
is not actually a deliverable file, we have to update the validation
tool to ignore it.

Story: #2001852
Task: #14347
Change-Id: I99bd94a323b53c0dfc2cb648268e51a30321cd46
Signed-off-by: Doug Hellmann <doug@doughellmann.com>

2018-04-20 14:05:04 -04:00

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

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.

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..present (Rocky Cycle key): key 0xc31292066be772022438222c184fd3e1edf21a78 (details)

References

reference/*

4.5 KiB Raw Blame History