dc84423b72
Following stestr's example where arguments such as --blacklist-file, --black-regex and --whitelist-file are deprecated since its 3.1.0 release, let's do the change here as well in order to get tempest consumers some time for the transition. This change deprecates the following arguments and replaces them by new ones which are functionally equivavelnt: * --black-regex is replaced by --exclude-regex * --blacklist-file is replaced by --exclude-list * --whitelist-file is replaced by --include-list For now, Tempest will accept both (new and old) arguments to make the transition smoother for all consumers. The patch also bumps min version of tox to 3.18.0 in order to replace tox's whitelist_externals by allowlist_externals option: https://github.com/tox-dev/tox/blob/master/docs/changelog.rst#v3180-2020-07-23 Change-Id: I3e09b31f63d2cd7ea41c48e62432bd3bc54fcf44
2.0 KiB
Stable Branch Support Policy
Since the Extended Maintenance policy for stable branches was adopted OpenStack projects will keep stable branches around after a "stable" or "maintained" period for a phase of indeterminate length called "Extended Maintenance". Prior to this resolution Tempest supported all stable branches which were supported upstream. This policy does not scale under the new model as Tempest would be responsible for gating proposed changes against an ever increasing number of branches. Therefore due to resource constraints, Tempest will only provide support for branches in the "Maintained" phase from the documented Support Phases. When a branch moves from the Maintained to the Extended Maintenance phase, Tempest will tag the removal of support for that branch as it has in the past when a branch goes end of life.
The expectation for Extended Maintenance phase branches is that they will continue running Tempest during that phase of support. Since the REST APIs are stable interfaces across release boundaries, branches in these phases should run Tempest from master as long as possible. But, because we won't be actively testing branches in these phases, it's possible that we'll introduce changes to Tempest on master which will break support on Extended Maintenance phase branches. When this happens the expectation for those branches is to either switch to running Tempest from a tag with support for the branch, or exclude a newly introduced test (if that is the cause of the issue). Tempest will not be creating stable branches to support Extended Maintenance phase branches, as the burden is on the Extended Maintenance phase branche maintainers, not the Tempest project, to support that branch.