Release requests and history tracking
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Zuul a716920a4e Merge "TripleO train ml3 release" 3 hours ago
data Merge "Add dtantsur and gtema as release liasons" 7 hours ago
deliverables Merge "TripleO train ml3 release" 3 hours ago
doc Merge "Fix typo: deatls -> details" 3 weeks ago
openstack_releases new-release: Drop tarball-base from individual releases 1 week ago
templates switch mailing lists to openstack-discuss 9 months ago
tools Fix bashate errors 2 months ago
.gitignore Switch to stestr 1 year ago
.gitreview OpenDev Migration Patch 5 months ago
.stestr.conf Switch to stestr 1 year ago
.zuul.yaml Add Python 3 Train unit tests 2 months ago
CONTRIBUTING.rst Document tag pipeline jobs in contributor doc 3 months ago
LICENSE Add top level LICENSE file 11 months ago
README.rst Point to release-management info in governance 10 months ago
bindep.txt install the python3 version of launchpadlib 1 year ago
requirements.txt Switch to ruamel for yaml handling 2 months ago
setup.cfg Merge "Add Python 3 Train unit tests" 1 month ago
setup.py tox setup 4 years ago
test-requirements.txt Switch to stestr 1 year ago
tox.ini Merge "Add Python 3 Train unit tests" 1 month ago
watched_queries.yml Rename review.openstack.org to review.opendev.org 4 months ago
yamllint.yml add linter rules for vertical whitespace 2 years ago

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.