Release requests and history tracking
Go to file
Hervé Beraud 355d3ca184 Proposing Wallaby RC1 for keystone
If you wants to wait for a specific patch to make it to the release,
someone from your team can -1 the patch to have it held, or update that patch
with a different commit SHA.

Patches with no response will be merged by Friday March 26.

$ git log --oneline --no-merges 18.0.0..ef711cd0e
9579c809d Add job for keystone functional protection tests
9707673b3 trivial: Update minor wording nit in RBAC persona documentation
a0ae615ab Clarify top-level personas in RBAC documentation
4df1130e1 Clarify ``reader`` role implementation in persona admin guide
256160b84 [goal] Deprecate the JSON formatted policy file
11cfc38df Ignore oslo.db deprecating sqlalchemy-migrate warning
c239cc666 Add openstack-python3-wallaby-jobs-arm64 job
f7df9fba8 Support bytes type in generate_public_ID()
9ef800f0b Imported Translations from Zanata
d6610594d Drop lower-constraints job
6e7369f2e fix E225 missing whitespace around operator
2d7bf10a5 Use app cred user ID in policy enforcement
b83170a38 Generalize release note for bug 1878938
5d2f716e4 Use enforce_new_defaults when setting up keystone protection tests
e98d1ac62 Implement more robust connection handling for asynchronous LDAP calls
5b0c2e010 Imported Translations from Zanata
f5348d3a2 Add vine to lower-constraints
5f546d03a Simplify default config test
5d7c92e20 Add support for functional RBAC tests
c1dcbb05b Delete system role assignments from system_assignment table

Signed-off-by: Hervé Beraud <hberaud@redhat.com>
Change-Id: I5763877cef99f76cbf2ddfb419dc306d0bdb2fd3
2021-03-19 13:38:59 +01:00
data Adding a new email for release liaison to hberaud 2021-03-09 08:58:06 +01:00
deliverables Proposing Wallaby RC1 for keystone 2021-03-19 13:38:59 +01:00
doc improve docs 2021-03-18 18:41:52 +01:00
openstack_releases Merge "fix nits" 2021-03-16 09:18:29 +00:00
templates Remove unused RC templates 2019-09-23 18:04:44 +02:00
tools Merge "Add delete option to list_eol_stale_branches.sh" 2021-03-08 11:25:40 +00: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 Switch to victoria job template 2020-06-02 14:28:30 -05:00
bindep.txt Cleanup bindep packages 2020-04-11 15:57:21 -05: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 Update README.rst for better looks 2019-11-13 16:51:02 +01:00
requirements.txt add reno semver-next to the list-changes output 2020-09-03 08:34:49 -04:00
setup.cfg Adding a tool to catch projects that missed branching 2021-03-03 13:51:12 +01:00
setup.py [Trivial] Remove executable privilege of setup.py 2016-05-09 16:38:37 +00:00
test-requirements.txt Update to latest hacking for pep8 checks 2020-07-27 16:33:03 -05:00
tox.ini Update to latest hacking for pep8 checks 2020-07-27 16:33:03 -05: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

OpenStack Releases

image

This repository is used to drive release automation for OpenStack release deliverables, ultimately publishing them on the https://releases.openstack.org/ website.

Changes to this repository are proposed using Gerrit at https://review.opendev.org. This repository is managed by the OpenStack Release Management team.

For more information on how to use this repository, please read our reference documentation.

Who should use this repository

All official OpenStack software should go through the OpenStack 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).

Deliverables managed by teams not under OpenStack governance should follow the tagging instructions in the infra manual.

More information

You can reach the Release Management team on the #openstack-release channel on Freenode IRC, or by sending an email with '[release]' as a subject prefix to the openstack-discuss mailing-list.