tree 5ec8515b48a75c4f751f6d04fafede37ab9486d7
parent a09be7e018c9e3b59cb4707b9146f336552b060d
author Masayuki Igawa <masayuki@igawa.io> 1600253721 +0900
committer Masayuki Igawa <masayuki@igawa.io> 1600344070 +0900
gpgsig -----BEGIN PGP SIGNATURE-----
 
 iQJGBAABCgAwFiEEwnwvADoqmZqQOnU9KQ9T7ciZv4kFAl9jUAYSHG1hc2F5dWtp
 QGlnYXdhLmlvAAoJECkPU+3Imb+JKsYQAKXCn/JqLBNXm1ws32uqnGFydigV56GM
 VYUWxYGgmK2I8XlAPmBmtVUIbVduFkcpkXVdh/zM75fJR/GxZ+FI/O7N4ehc8Fci
 qkMyaEGmkAlmkb0TE+fJq0wMGA43nWo24WgN0zt/eKd2dmo1GTwuQLNEtb4C6BA/
 O3rdCW3GsPOjPzlez88vpKek0UbiwYe5JB9kKvp99p7XSrdvII3QV9jqV5WG3L7u
 EHOA+SK5YotSmvp6DkaMm4av6RfzTtL2VGc8aMGvSUzVixgNNsslyESGyQxHZ5ju
 Z+pP69wQjNMsdi+Dr/ld6dYTgcH1zGkCPIvSLx9bkHykoWnVBMC1q+KuzT7D1XmS
 EIGulCkCwcUW/9RCz/8zK/Nce89MJQoB2hu2rsZC4qYWx2zTEWVUjoFxcIHCCfvb
 esyCWcjCIqC+fQLKhlNmwDezj9nAmdUMWFFWwUxUnAj4n12xztVehaKlpG0lg9+o
 NwUqECF1JMp90boOdtXs+MRzDguy8STXGgh/snVET9aHxauPHsmsYpCE+jqSGcay
 OK1MOER1EIDvTK2r6+k2N+kflTi8feB2o7ymtdE7OQCFDWKOSsEFZlmjAz7D7AbG
 I5tLAIDgiFHKbdt8344i9Gj+g7WLacAz3FyhFmoR8UkuqLR3QI4ZOU08NOO3hLbf
 Rafl4tJdXrkx
 =WtAO
 -----END PGP SIGNATURE-----

Use stable constraint in tox to release new tag for Victoria

We are going to release Tempest new tag to declare the start of support
for stable/victoria. So that new tag use stable/victoria constraint in
the tox env.

For example, if anyone use Tempest 25.0.0 in future, let's say 1 year
later then tox env also should use the victoria constraint for
compatibility instead of master.

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

By using master constraint in tox for all the old tag is problem and we
faced the issue of constraint incompatibility due to that and we have to
workaround it all over the devstack, tempest role, grenade to set the
stable constraint via env var.

Further information:
 https://docs.openstack.org/tempest/latest/requirement_upper_constraint_for_tempest.html

Change-Id: I1f8c788327b4a1a7f804cf01f8c22609e6646dd9