---- On Mon, 13 Aug 2018 23:01:33 +0900 Doug Hellmann <d...@doughellmann.com>
wrote ----
> Excerpts from Dmitry Tantsur's message of 2018-08-13 15:51:56 +0200:
> > On 08/13/2018 03:46 PM, Doug Hellmann 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.
> >
> > Okay, thank you for clarification. I stand corrected and apologize if my
> > frustration was expressed too loudly or harshly :)
>
> Not at all. This is new territory, and we made a decision somewhat
> quickly, so I am not surprised that we need to do a little more work to
> communicate the results.
>
> >
> > >
> > > 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.
> >
> > Okay, this makes sense now.
>
> Good.
>
> Now, we just need someone to figure out where to write all of that down
> so we don't have to have the same conversation next cycle. :-)
+1, this is very imp. I was discussing the same with amotoki today on QA
channel. I have added a TODO for me to write the 1. "How Plugins should cover
the stable branch testing with branchless repo" now i can add 2nd TODO also 2.
"Release model & tagging clarification of Tempest Plugins". I do not know the
best common place to add those doc but as start i can write those in Tempest
doc and later we can refer/move the same on Plugins side too.
I have added this TODO on qa stein ptg etherpad also for reminder/feedback-
https://etherpad.openstack.org/p/qa-stein-ptg
-gmann
>
> Doug
>
> >
> > >
> > > 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-requ...@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-requ...@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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
