openstack/releases
Code Issues Proposed changes
Release requests and history tracking
13,050 Commits 1 Branch 0 Tags 128 MiB
Python 89.7%
Shell 10.3%
a4a3cd7532
Go to file
Dmitriy Rabotyagov a4a3cd7532 Create train branch for os_murano role 
As Murano has been merged after branching, but was announced and
OSA is lagging behind, it's probably worth to branch murano
for train.

Change-Id: I7334d1671410160df9f235a53af6c7dbade7a96c
2019-11-13 14:28:52 +00:00
data remove dhellmann as release liaison 2019-11-02 10:03:24 -04:00
deliverables Create train branch for os_murano role 2019-11-13 14:28:52 +00:00
doc Merge "Drop redundant Manila deadline" 2019-11-12 11:28:26 +00:00
openstack_releases Merge "Be explicit about python3 executable" 2019-10-24 09:34:46 +00:00
templates Remove unused RC templates 2019-09-23 18:04:44 +02:00
tools Be explicit about python3 executable 2019-10-16 09:45:29 -05:00
.gitignore Switch to stestr 2018-07-10 10:38:33 +07:00
.gitreview OpenDev Migration Patch 2019-04-19 19:37:48 +00:00
.stestr.conf Switch to stestr 2018-07-10 10:38:33 +07:00
.zuul.yaml Switch to Ussuri jobs 2019-10-25 10:58:27 +08:00
bindep.txt install the python3 version of launchpadlib 2018-06-21 16:28:06 -04:00
CONTRIBUTING.rst Document tag pipeline jobs in contributor doc 2019-06-06 12:10:45 +02:00
LICENSE Add top level LICENSE file 2018-10-17 10:36:04 +11:00
README.rst Point to release-management info in governance 2018-11-01 16:09:48 +01:00
requirements.txt Switch to ruamel for yaml handling 2019-07-08 11:40:11 -05:00
setup.cfg Merge "Add Python 3 Train unit tests" 2019-08-08 09:50:12 +00:00
setup.py [Trivial] Remove executable privilege of setup.py 2016-05-09 16:38:37 +00:00
test-requirements.txt Switch to stestr 2018-07-10 10:38:33 +07:00
tox.ini Merge "Add Python 3 Train unit tests" 2019-08-08 09:50:12 +00:00
watched_queries.yml Rename review.openstack.org to review.opendev.org 2019-05-12 04:33:25 +08:00
yamllint.yml add linter rules for vertical whitespace 2017-07-31 17:26:33 -04:00

README.rst

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.