Jean-Philippe Evrard 55d3c0a6a4 Make Dmitriy release liaison for OSA
As I have stepped out, and trained noonedeadpunk for release
business, I now have the impression I can remove this from my belt.

I trust him to do the right thing, and he can ask for my help if
necessary.

Change-Id: I935c855886fd2bef61ef3c23453f06ac2b14955d
2019-11-13 11:48:21 +01:00
2019-11-13 11:48:21 +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
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 134 MiB
Languages
Python 89.1%
Shell 10.9%