We are glad to announce the release of: placement 11.0.0 This release is part of the caracal release series. The source is available from: https://opendev.org/openstack/placement Download the package from: https://pypi.org/project/placement Please report issues through: https://storyboard.openstack.org/#!/project/openstack/placement For more details, please see below. Changes in placement 10.0.0..11.0.0 ----------------------------------- a6411672 reno: Update master for unmaintained/xena d64f8b0f reno: Update master for unmaintained/wallaby 5c4c51de reno: Update master for unmaintained/victoria 8e705fa4 reno: Update master for unmaintained/yoga 4d61af64 Add upgrade job from 2023.1 e10099bd Bump hacking 1001769d Update python classifier in setup.cfg 13ceadd2 Add job to test with SQLAlchemy master (2.x) d638b011 db: Wrap raw SQL query in sqlalchemy.text 141780c0 Update master for stable/2023.2 56778d26 Changed /tmp/migrate-db.rc to /root/migrate-db.rc Diffstat (except docs and test files) ------------------------------------- .zuul.yaml | 20 ++++++++++++++++++++ placement/objects/resource_class.py | 4 +++- releasenotes/source/2023.2.rst | 6 ++++++ releasenotes/source/index.rst | 1 + releasenotes/source/victoria.rst | 2 +- releasenotes/source/wallaby.rst | 2 +- releasenotes/source/xena.rst | 2 +- releasenotes/source/yoga.rst | 2 +- requirements.txt | 4 ---- setup.cfg | 2 ++ test-requirements.txt | 6 +----- 12 files changed, 40 insertions(+), 17 deletions(-) Requirements updates -------------------- diff --git a/requirements.txt b/requirements.txt index 6842b282..684ee1a3 100644 --- a/requirements.txt +++ b/requirements.txt @@ -5,4 +4,0 @@ -# The order of packages is significant, because pip processes them in the order -# of appearance. Changing the order has an impact on the overall integration -# process, which may cause wedges in the gate later. - diff --git a/test-requirements.txt b/test-requirements.txt index 29383c0d..157d7616 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -1,5 +1 @@ -# The order of packages is significant, because pip processes them in the order -# of appearance. Changing the order has an impact on the overall integration -# process, which may cause wedges in the gate later. - -hacking>=4.0.0,<4.1.0 # Apache-2.0 +hacking>=6.1.0,<6.2.0 # Apache-2.0