Go to file
Thierry Carrez 0e9086ae98 cycle-with-intermediary release process details
Relax release process for cycle-with-intermediary deliverables,
while still ensuring that:

- they are encouraged to release multiple times
- they are encouraged to switch to cycle-with-rcs if they
  routinely only release once
- they are released at least once before RC1

Change-Id: I2c49559f113f938dfaefd925d5fcc49d60da5828
2019-08-09 12:02:20 +02:00
2019-07-01 14:54:16 +01:00
2019-07-08 11:46:30 -05: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-07-19 14:43:41 -04:00
2018-10-17 10:36:04 +11:00
2018-07-10 10:38:33 +07:00
2019-08-08 09:50:12 +00:00

Using This Repository

All official OpenStack software should go through the 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).

This repository is used to track release requests. Releases are managed using groups of "deliverables", made up of individual project repositories sharing a Launchpad group and a version number history. Many deliverables will only have one constituent project repository.

The repository is managed by the Release Management team.

image

Refer to the reference documentation for more details

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

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