openstack/releases
Code Issues Proposed changes
Release requests and history tracking
10,566 Commits 1 Branch 0 Tags 129 MiB
Python 89.7%
Shell 10.3%
8b22203874
Go to file
Kota Tsuyuzaki 8b22203874 Storlets Stein M-3 release 
Though, it's first release in the Stein cycle.
We're planning to have another RC1 release in this cycle.

Change-Id: I93772fb867a9c58ee977e57e67030a9e64855a07
2019-03-08 16:17:47 +09:00
deliverables Storlets Stein M-3 release 2019-03-08 16:17:47 +09:00
doc Merge "Proposed release schedule for Train" 2019-03-07 17:12:31 +00: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 Use env python instead of /usr/bin/python 2019-03-04 20:20:59 +01: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 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 [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 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.

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.