Open Stack

// jim

On Mon, Aug 13, 2018 at 9:46 AM, Doug Hellmann <doug at doughellmann.com>
wrote:

> Excerpts from Dmitry Tantsur's message of 2018-08-13 15:35:23 +0200:
> > Hi,
> >
> > The plugins are branchless and should stay so. Let us not dive into this
> madness
> > again please.
>
> You are correct that we do not want to branch, because we want the
> same tests running against all branches of services in our CI system
> to help us avoid (or at least recognize) API-breaking changes across
> release boundaries.
>
> We *do* need to tag so that people consuming the plugins to certify
> their clouds know which version of the plugin works with the version
> of the software they are installing. Newer versions of plugins may
> rely on features or changes in newer versions of tempest, or other
> dependencies, that are not available in an environment that is
> running an older cloud.
>
> We will apply those tags in the series-specific deliverable files in
> openstack/releases so that the version numbers appear together on
> releases.openstack.org on the relevant release page so that users
> looking for the "rocky" version of a plugin can find it easily.
>

Thanks Doug. My confusion was around the cycle-with-intermediary model,
which I thought implied a stable branch. Tagging at end of cycle seems
fine to me. :)

// jim
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20180813/babc93c2/attachment.html>