tree a930e4e513cf4fd27c8d70b344d9a6bbabe5f7f4
parent b04b102984fa16f4837f63e322baf472c1c76609
author Ghanshyam Mann <gmann@ghanshyammann.com> 1678996238 -0500
committer Ghanshyam Mann <gmann@ghanshyammann.com> 1678996238 -0500

Use stable constraint in tox to release new tag for 2023.1

We will release Tempest new tag to get cinder tests
fix[1] in stable/2023.1. Without the cinder test fix[1], tempest
released for 2023.1 will not work with cinder in 2023.1.
So that new tag use stable/2023.1 constraint in the tox env.

For example: if anyone uses Tempest new tag in future say
1 year later then tox env also should use the 2023.1 contstraint for
compatibility instead master.

These need to be move back to master constraint once release is done.

[1] https://review.opendev.org/c/openstack/tempest/+/875372

Change-Id: Ibb348e0642190b3a83d8b5f86c8b49295cf071e0