Open Stack

On Tue, 26 Jun 2018, 1:08 pm Thierry Carrez, <thierry at openstack.org> wrote:

> Dmitry Tantsur wrote:
> > [...]
> > My suggestion: tempest has to be compatible with all supported releases
> > (of both services and plugins) OR be branched.
> > [...]
> I tend to agree with Dmitry... We have a model for things that need
> release alignment, and that's the cycle-bound series. The reason tempest
> is branchless was because there was no compatibility issue. If the split
> of tempest plugins introduces a potential incompatibility, then I would
> prefer aligning tempest to the existing model rather than introduce a
> parallel tempest-specific cycle just so that tempest can stay
> release-independent...
>
> I seem to remember there were drawbacks in branching tempest, though...
> Can someone with functioning memory brain cells summarize them again ?
>


Branchless Tempest enforces api stability across branches.

For the same reason tempest plug ins should be branchless, which is one of
the reasons that having them in the same repo as a service was an issue:
services are branched but api/integration tests should be branchless.

Andrea


> --
> Thierry Carrez (ttx)
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20180626/87928715/attachment.html>