Release requests and history tracking
Go to file
Chris Friesen 121086b5d1 Release os-traits 0.11.0
I'd like to propose what is effectively a Stein milestone-2 release
for os-traits to release merged commits since the last release.

Among other things this would make available some new traits for
virtual TPM and AMD secure virtualization.

Note that +1 from the PTL or release liason is needed, I am not either.

Change-Id: I9c2110a6c3cf90aac4976c07e994edae2a0aba0a
2019-02-08 15:09:34 -06:00
deliverables Release os-traits 0.11.0 2019-02-08 15:09:34 -06:00
doc Allow user to generate urls for the given results. 2019-02-01 15:10:23 +01:00
openstack_releases replace legacy-manila-publishimage-generic job 2019-01-22 05:58:40 -05:00
templates switch mailing lists to openstack-discuss 2018-12-04 10:41:28 -05:00
tools Merge "Allow user to generate urls for the given results." 2019-02-07 10:29:40 +00: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 Add script to facilitate MembershipFreeze handling 2019-01-16 22:34:21 +01: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

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.