Go to file

Thierry Carrez 038e855fb1 Reorder steps on RC1 week process

For RC1 week the steps are roughly in chronological order.
In order to get cycle-highlights in time for the deadline,
move that point up.

Change-Id: I40fd38599b0851dd596f9669edd8d26ccedd8c2a

2019-03-14 17:50:22 +01:00

deliverables

Merge "TripleO: minor release for rocky"

2019-03-14 10:32:25 +00:00

doc

Reorder steps on RC1 week process

2019-03-14 17:50:22 +01:00

openstack_releases

only fail pypi permission validation if the project exists

2019-03-07 18:03:58 -06:00

templates

switch mailing lists to openstack-discuss

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

tools

Put the lists under a directory

2019-03-12 20:06:17 +01: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

…

yamllint.yml

…

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.