Go to file

gaobin 5c7551c69c Modify the marged to meraged

Change-Id: I6ae372a41523b3a1b265674a7afa149d1caad4c3

2018-12-13 12:08:52 +08:00

deliverables

Merge "Release OpenStack-Ansible rocky/18.1.1"

2018-12-13 00:53:56 +00:00

doc

Modify the marged to meraged

2018-12-13 12:08:52 +08:00

openstack_releases

quiet reno logging in list-changes

2018-12-05 16:51:18 -05:00

templates

switch mailing lists to openstack-discuss

2018-12-04 10:41:28 -05:00

tools

add a script to get a list of unreleased changes for a team

2018-11-19 12:57:18 -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

Switch to "tox -e docs"

2018-11-05 20:58:02 +01: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

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

update to use openstack_governance library

2018-11-21 15:10:34 -05:00

setup.cfg

switch mailing lists to openstack-discuss

2018-12-04 10:41:28 -05: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 "Don't quote {posargs} in tox.ini"

2018-10-21 05:30:16 +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

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.

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.