Release requests and history tracking
Go to file
Akihiro Motoki 6ca37129eb Update bug trackers of OSC and SDK
OSC and SDK teams use storyboard as bug trackers.
This commit updates the bug tracker information.

The bug tracker of openstacksdk was wrong.
It pointed to openstack/shade (760). It is also fixed.

Change-Id: Ia06ae76d3d030bab4c9c967d3789fd0a1786ae62
2019-10-25 17:10:23 +09:00
data Add Mark Goddard as an ironic release liaison 2019-10-23 06:58:33 -07:00
deliverables Update bug trackers of OSC and SDK 2019-10-25 17:10:23 +09:00
doc Merge "Add note to highlights page explaining content" 2019-10-24 09:31:48 +00:00
openstack_releases Merge "Be explicit about python3 executable" 2019-10-24 09:34:46 +00:00
templates Remove unused RC templates 2019-09-23 18:04:44 +02:00
tools Be explicit about python3 executable 2019-10-16 09:45:29 -05: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 timeout" 2019-10-24 12:44:33 +02: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
bindep.txt install the python3 version of launchpadlib 2018-06-21 16:28:06 -04:00
requirements.txt Switch to ruamel for yaml handling 2019-07-08 11:40:11 -05:00
setup.cfg Merge "Add Python 3 Train unit tests" 2019-08-08 09:50:12 +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 Merge "Add Python 3 Train unit tests" 2019-08-08 09:50:12 +00: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.

image

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.