Use stable constraint in tox to release new tag for Xena
We are going to release Tempest a new tag to declare the start of
support for stable/xena so the new tag should use stable/xena
constraint in the tox env.
For example: if anyone uses Tempest 29.0.0 in the future, say 1 year
later, then tox env also should use the xena contstraint instead
master for the compatibility.
These changes need to be moved back to master constraint once the
release is done. Using master constraint in tox.ini for all the older
tags is a problem and we faced the issue of constraint
incompatibility. Therefore, we have to work around it all over the
devstack, tempest, grenade and set the stable constraints via the
env var.
Change-Id: I2bbf550294e7873eb07598b204ccc8d63ff6b5eb
1 file changed