openstack/releases
Code Issues Proposed changes
Release requests and history tracking
9,708 Commits 1 Branch 0 Tags 131 MiB
Python 89.1%
Shell 10.9%
65c449c542
Go to file
Zuul 65c449c542 Merge "clarify debug logging for test fixtures"
2018-10-11 02:39:21 +00:00
deliverables Merge "reno 2.11.2" 2018-10-10 20:33:25 +00:00
doc remove warnings from using deprecated methods of Sphinx application 2018-10-09 11:08:48 -04:00
openstack_releases Merge "clarify debug logging for test fixtures" 2018-10-11 02:39:21 +00:00
templates Update and replace http with https for doc links in releases doc 2017-08-09 14:10:09 +00:00
tools Script to list unreleased and open changes 2018-09-21 14:45:30 +02:00
.gitignore Switch to stestr 2018-07-10 10:38:33 +07:00
.gitreview Added .gitreview 2015-07-02 09:25:52 +00:00
.stestr.conf Switch to stestr 2018-07-10 10:38:33 +07:00
.zuul.yaml add python 3.6 unit test job 2018-08-30 14:56:02 -04:00
bindep.txt install the python3 version of launchpadlib 2018-06-21 16:28:06 -04:00
CONTRIBUTING.rst Base ladder content for CONTRIBUTING.rst 2018-03-22 16:10:28 +01:00
README.rst move the submission guide out of the readme to the reference docs 2018-06-28 17:26:41 -04:00
requirements.txt Remove duplicate packaging 2018-03-08 14:29:25 +11:00
setup.cfg Merge "add a script to examine the gerrit acls for issues" 2018-03-05 15:00:34 +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 "configure oslotest for debug output" 2018-10-11 02:35:22 +00:00
watched_queries.yml remove extra blank line in watched query output 2017-08-04 10:26:22 -04:00
yamllint.yml add linter rules for vertical whitespace 2017-07-31 17:26:33 -04:00

README.rst

Using This Repository

This repository is for tracking release requests for OpenStack projects. The 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.

The repository is managed by the Release Management team.

image

Refer to the reference documentation for more details