Go to file
Thierry Carrez f33b0d3358 Update process for R+1 week
Move R+1 week process items to the top of the document, remove obsolete
steps and merge the remaning ones with pre-PTG steps. Include weekly
email content. Move the step about proposing a schedule for the next
release to "between m-2 and m-3", as this is when we actually do that.

Change-Id: I5a4a7e5e059156139944a09e4d7813bd11ec1c5a
2019-11-14 14:47:50 +01:00
2019-11-02 10:03:24 -04:00
2019-11-14 14:47:50 +01:00
2019-09-23 18:04:44 +02:00
2018-07-10 10:38:33 +07:00
2019-04-19 19:37:48 +00:00
2018-07-10 10:38:33 +07:00
2019-10-25 10:58:27 +08:00
2018-10-17 10:36:04 +11:00
2019-11-13 16:51:02 +01:00
2018-07-10 10:38:33 +07:00
2019-08-08 09:50:12 +00:00

OpenStack Releases

image

This repository is used to drive release automation for OpenStack release deliverables, ultimately publishing them on the https://releases.openstack.org/ website.

Changes to this repository are proposed using Gerrit at https://review.opendev.org. This repository is managed by the OpenStack Release Management team.

For more information on how to use this repository, please read our reference documentation.

Who should use this repository

All official OpenStack software should go through the OpenStack Release Management team team to produce releases. Exceptions to this rule are granted by the Technical Committee and documented in the openstack/governance repository ('release-management' key in reference/projects.yaml).

Deliverables managed by teams not under OpenStack governance should follow the tagging instructions in the infra manual.

More information

You can reach the Release Management team on the #openstack-release channel on Freenode IRC, or by sending an email with '[release]' as a subject prefix to the openstack-discuss mailing-list.

Description
Release requests and history tracking
Readme 142 MiB
Languages
Python 89.1%
Shell 10.9%