Open Stack

 ---- On Mon, 13 Aug 2018 22:46:42 +0900 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 for clarifying it again :). Details can be found on original ML[1] also about goal behind tagging the plugins. Next item pending on branchless testing is to setup the Plugin CI jobs for stable branches also like Tempest does. That is one item for QA team to help plugins in stein. 

[1] http://lists.openstack.org/pipermail/openstack-dev/2018-June/131810.html

-gmann
> 
 > Doug
 > 
 > > 
 > > Dmitry
 > > 
 > > On 08/12/2018 10:41 AM, Ghanshyam Mann wrote:
 > > > Hi All,
 > > > 
 > > > Rocky release is few weeks away and we all agreed to release Tempest plugin with cycle-with-intermediary. Detail discussion are in ML [1] in case you missed.
 > > > 
 > > > This is reminder to tag your project tempest plugins for Rocky release. You should be able to find your plugins deliverable file under rocky folder in releases repo[3].  You can refer cinder-tempest-plugin release as example.
 > > > 
 > > > Feel free to reach to release/QA team for any help/query.
 > > 
 > > Please make up your mind. Please. Please. Please.
 > > 
 > > > 
 > > > [1] http://lists.openstack.org/pipermail/openstack-dev/2018-June/131810.html
 > > > [2] https://review.openstack.org/#/c/590025/
 > > > [3] https://github.com/openstack/releases/tree/master/deliverables/rocky
 > > > 
 > > > -gmann
 > > > 
 > > > 
 > > > 
 > > > __________________________________________________________________________
 > > > 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
 > > > 
 > > 
 > 
 > __________________________________________________________________________
 > 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
 >