Release requests and history tracking
Go to file
Sean McGinnis 0ddad8a083 Force ceilometermiddleware 1.3.0 release
There were a couple CI related commits since last cycle
that we should tag before branching so they do not need
to be backported.

Change-Id: I439ab6c986a260c7326d5cd8eb05078649a6e830
2018-07-20 11:33:41 -05:00
deliverables Force ceilometermiddleware 1.3.0 release 2018-07-20 11:33:41 -05:00
doc Merge "Add Stein PTL election details to the schedule" 2018-07-19 23:54:34 +00:00
openstack_releases fix the calculation used for finding release history 2018-07-19 11:52:07 -04:00
templates Update and replace http with https for doc links in releases doc 2017-08-09 14:10:09 +00:00
tools Remove Rally from aclfixer exceptions 2018-06-29 14:13:11 +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 change the timeouts for the validate and list-changes jobs 2018-04-16 15:50:45 -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 Switch to stestr 2018-07-10 10:38:33 +07: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

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