Go to file

Thierry Carrez 6f0dc28878 Document tag pipeline jobs in contributor doc

While debugging a release failure this morning I realized that
the magic job diagram was missing the release notes publication
jobs that are in the "tag" pipeline.

Change-Id: I2879de0df530ccf96ac4be61c42ce07472399b4e

2019-06-06 12:10:45 +02:00

deliverables

Merge "Release ironic 10.1.9 for Queens"

2019-06-06 06:34:16 +00:00

doc

Merge "Switch constraints files over to the new opendev infrastructure"

2019-05-28 15:09:19 +00:00

openstack_releases

Switch constraints files over to the new opendev infrastructure

2019-05-22 14:33:37 +10:00

templates

switch mailing lists to openstack-discuss

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

tools

Rename review.openstack.org to review.opendev.org

2019-05-12 04:33:25 +08:00

.gitignore

Switch to stestr

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

.gitreview

OpenDev Migration Patch

2019-04-19 19:37:48 +00:00

.stestr.conf

Switch to stestr

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

.zuul.yaml

Revert "Increase tag-releases job timeout"

2019-04-16 14:13:40 +00:00

bindep.txt

install the python3 version of launchpadlib

2018-06-21 16:28:06 -04:00

CONTRIBUTING.rst

Document tag pipeline jobs in contributor doc

2019-06-06 12:10:45 +02: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

Use recommended twine check for README validation

2019-04-05 10:56:16 -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

Add a 'generic' release-type.

2019-04-18 15:27:27 +10:00

watched_queries.yml

Rename review.openstack.org to review.opendev.org

2019-05-12 04:33:25 +08: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.