Go to file

Jean-Philippe Evrard 5f3520121c First release of ansible-config_template

Ansible config_template is not like the usual roles of
openstack-ansible. Its purpose is to be reused in different
projects (including outside openstack), and maybe branched
per ansible version in the future. The best release model
to match this purpose would be _independant.

Change-Id: I5643a37414c5e44c96f441e40a94656e5394190c

2019-04-04 14:19:13 +02:00

deliverables

First release of ansible-config_template

2019-04-04 14:19:13 +02:00

doc

Merge "Add TOC for release deliverables"

2019-04-01 00:25:52 +00:00

openstack_releases

Merge "Extract announce info from deliverable file"

2019-03-27 11:00:37 +00:00

templates

switch mailing lists to openstack-discuss

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

tools

add a tool to show changes in rc-based repos

2019-03-27 13:54:24 -04:00

.gitignore

Switch to stestr

2018-07-10 10:38:33 +07:00

.gitreview

…

.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

Merge "Fix WordCompleter import"

2019-01-10 18:32:07 +00:00

setup.cfg

switch mailing lists to openstack-discuss

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

setup.py

…

test-requirements.txt

Switch to stestr

2018-07-10 10:38:33 +07:00

tox.ini

Use a template to generate the 'whereto' testing data

2019-03-02 15:31:01 +11: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.