At the end of the Icehouse cycle we decided that branches in Tempest were actually inhibiting the project goals of being a test suite that works equally well in any OpenStack environment. Too many assumptions were being made about running with the same branch of OpenStack. While this works fine for the gate, and for Linux distros, it actually maps very poorly to public clouds, or any CDing environment. So there is no stable/icehouse Tempest branch, and will not be another new stable branch in the future.
This discussion will include some time to explain why we did this, and the major implications. It will primarily be about the remaining steps to handle all situations with branchless Tempest. Topics we expect to cover:
* Remaining devstack-gate work to do extension selection per branch * Tempest releases (we should still probably do releases for end user convenience, what kind of timecycle should those be on?) * How and when to deprecate / remove code from Tempest now that it must run on multiple upstream branches * What kinds of feature flags we believe we should have * Configuration compatibility guaruntees (now that we're going to have a bunch of options that deployers need to set).