Go to file

Force release python-karborclient for rocky

Forces release of committed changes this cycle and creates a
stable/rocky branch.

Change-Id: I89172468471f7c1700ea713e856dfc0f3cf9ac90
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>

2018-08-10 11:49:10 -05:00

deliverables

Force release python-karborclient for rocky

2018-08-10 11:49:10 -05:00

doc

Merge "Adjust missed branching process"

2018-08-08 09:27:27 +00:00

openstack_releases

Merge "add tempest plugins to the version listing page"

2018-08-10 09:31:35 +00:00

templates

Update and replace http with https for doc links in releases doc

2017-08-09 14:10:09 +00:00

tools

Remove unused --etherpad opt from list_weeks

2018-08-06 16:35:48 -05: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

Move zuul jobs in-repo

2018-07-21 13:41:46 -05: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

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.

Refer to the reference documentation for more details