cbee52e343
This reverts commit d84fbc1ec27f5249f31f060de16c8f67b3050a2d. Keeping Python 3.10 in setup.cfg classifier and zuul.yaml changes. Reason for revert: Needed-By: https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/882175 TC has been discussing about re-adding the python 3.8 testing in current master 2023.2 release testing. - https://meetings.opendev.org/meetings/tc/2023/tc.2023-04-25-18.00.log.html#l-191 - https://lists.openstack.org/pipermail/openstack-discuss/2023-April/033469.html While governance changes are under review, TC agreed to add py3.8 testing so that we do not see more project/lib dropping python 3.8 and make them uninstalable on python 3.8 - https://meetings.opendev.org/meetings/tc/2023/tc.2023-05-02-18.00.log.html#l-17 - https://review.opendev.org/c/openstack/governance/+/882165 Also adding py3.8 testing back in job https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/882175 Change-Id: Ibd373a944b42ae075d62b3e02a353787b9730d08
oslo.upgradecheck
Common code for writing OpenStack upgrade checks
This project contains the common code necessary for writing upgrade checks in OpenStack projects. It includes a module (oslo_upgradecheck.upgradecheck) for the common code as well as an example (oslo_upgradecheck.__main__) of integrating that code into a project.
- Free software: Apache license
- Documentation: https://docs.openstack.org/oslo.upgradecheck/latest/
- Source: https://opendev.org/openstack/oslo.upgradecheck
- Bugs: https://bugs.launchpad.net/oslo.upgradecheck