Hervé Beraud c81db5817b Release oslo.upgradecheck for Xena-1 milestone
This is a library release for ososlo.upgradecheck for the Xena-1
milestone. This repo includes commits that have not been releases for
this cycle yet.

If the team is ready to process with this release, please leave a +1
to indicate we should go ahead with the release.

If the team needs more time for things about to merge, or if there is
some other reason a release should not be done at this time, please
leave a -1 with a comment indicating the status. Then update the patch
with the new commit hash to use once the team is ready to do the
release.

$ git log --oneline --no-merges 1.3.0..3ca8698
75fe376 Move flake8 as a pre-commit local target.
276ecd7 Add Python3 xena unit tests
db3e3a9 Update master for stable/wallaby
8a43c37 Remove lower-constraints remnants
f234316 Uncap PrettyTable
456bd85 Remove six
a962943 Dropping lower constraints testing
20b199e Use TOX_CONSTRAINTS_FILE
09c42be Use py3 as the default runtime for tox

Signed-off-by: Hervé Beraud <hberaud@redhat.com>
Change-Id: I08b56d3dac10382af01b02dc8240ac4ad9734e6b
2021-05-25 12:14:34 +02:00
2019-09-23 18:04:44 +02:00
2018-07-10 10:38:33 +07:00
2019-04-19 19:37:48 +00:00
2018-07-10 10:38:33 +07:00
2020-06-02 14:28:30 -05:00
2020-04-11 15:57:21 -05:00
2018-10-17 10:36:04 +11:00
2019-11-13 16:51:02 +01:00
2021-04-20 14:57:51 +08: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.

Description
Release requests and history tracking
Readme 132 MiB
Languages
Python 89.1%
Shell 10.9%