Release requests and history tracking
Go to file
Hervé Beraud 06b1ed1b4a Proposing Wallaby RC1 for mistral
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 11.0.0..3c83837f
de4d0277 remove unicode from code
328988ed Drop lower-constraints job
421f8433 Fix a field name in the CodeSource class sample
c00bf32a Fix action heartbeat checker test
4319dbcb Add API docs for code sources and dynamic actions
7cf2014c [goal] Deprecate the JSON formatted policy file
ef162b9e Fix version of requests in constraints
b3f609d1 Update doc8 version
6b0ff4b6 Delete redundant print()
1c44a2b1 Fix constraints
a73fe5b8 Fix dynamic actions further
f78f3350 Code improvements after the dynamic actions patch
9be4f8e1 created a new Api endpoints and added dynamic actions
bce07476 Update TOX_CONSTRAINTS_FILE
f0bc4366 The encoding parameter in json.loads has been removed in py3.9
0d3509e2 Import HTTPStatus instead of http_client
2cd44558 [doc]Fix invalid url link
87c63f42 Remove a TODO comment about saving an action spec
d81dc75a Remove the module mistral/actions/action_factory.py
1d70823c Address a TODO comment in the legacy action provider test
175e5fd5 Add Python3 wallaby unit tests
0a74fb36 Update master for stable/victoria

Signed-off-by: Hervé Beraud <hberaud@redhat.com>
Change-Id: I7a1c6c374db75374aed96b1882ada28418ae1937
2021-03-19 14:01:39 +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 mistral 2021-03-19 14:01:39 +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.