Re: [openstack-dev] [releases][rocky][tempest-plugins][ptl] Reminder to tag the Tempest plugins for Rocky release
On Sun, Aug 12, 2018 at 05:41:20PM +0900, 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. > > [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 > It should also be noted that these repos will need to be set up with a release job if they do not already have one. They will need either publish-to-pypi or publish-to-pypi-python3, similar to what was done here: https://review.openstack.org/#/c/587623/ And before that is done, please make sure the package is registered and set up correctly on pypi following these insructions: https://docs.openstack.org/infra/manual/creators.html#pypi Requests to create a tempest plugin release will fail validation if this has not be set up ahead of time. Thanks, Sean __ 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
Re: [openstack-dev] [releases][rocky][tempest-plugins][ptl] Reminder to tag the Tempest plugins for Rocky release
Excerpts from Ghanshyam Mann's message of 2018-08-13 23:12:51 +0900: > > > > On Mon, 13 Aug 2018 23:01:33 +0900 Doug Hellmann > 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 We have a reference page for deliverable types in the releases repository (https://releases.openstack.org/reference/deliverable_types.html). That could be a place to talk about the tagging and branching expectations. It doesn't cover tempest-plugins at all, yet. Doug __ 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
Re: [openstack-dev] [releases][rocky][tempest-plugins][ptl] Reminder to tag the Tempest plugins for Rocky release
On Mon, 13 Aug 2018 23:01:33 +0900 Doug Hellmann 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
Re: [openstack-dev] [releases][rocky][tempest-plugins][ptl] Reminder to tag the Tempest plugins for Rocky release
On Mon, 13 Aug 2018 22:46:42 +0900 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. > > 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-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
Re: [openstack-dev] [releases][rocky][tempest-plugins][ptl] Reminder to tag the Tempest plugins for Rocky release
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. :-) 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
Re: [openstack-dev] [releases][rocky][tempest-plugins][ptl] Reminder to tag the Tempest plugins for Rocky release
Excerpts from Jim Rollenhagen's message of 2018-08-13 09:50:34 -0400: > // jim > > On Mon, Aug 13, 2018 at 9:46 AM, 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. > > > > 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 Normally cycle-with-intermediary would imply a branch, but it's really focused more around the releases than the branching. There's a separate flag that most deliverables don't need to use that controls the branching policy, and in this case we treat these repos as branchless. Doug __ 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
Re: [openstack-dev] [releases][rocky][tempest-plugins][ptl] Reminder to tag the Tempest plugins for Rocky release
On Mon, 13 Aug 2018 22:35:23 +0900 Dmitry Tantsur wrote > Hi, > > The plugins are branchless and should stay so. Let us not dive into this > madness > again please. > > 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. Not sure why it is being understood as to cut the branch for plugins. This thread is just to remind plugins owner to tag the plugins for Rocky release. 'cycle-with-intermediary' does not need to be cut the branch always, for plugins and tempest it is just to release a tag for current OpenStack release. -gmann > > > > > [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
Re: [openstack-dev] [releases][rocky][tempest-plugins][ptl] Reminder to tag the Tempest plugins for Rocky release
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 :) 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. 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
Re: [openstack-dev] [releases][rocky][tempest-plugins][ptl] Reminder to tag the Tempest plugins for Rocky release
// jim On Mon, Aug 13, 2018 at 9:46 AM, 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. > > 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 __ 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
Re: [openstack-dev] [releases][rocky][tempest-plugins][ptl] Reminder to tag the Tempest plugins for Rocky release
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. 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
Re: [openstack-dev] [releases][rocky][tempest-plugins][ptl] Reminder to tag the Tempest plugins for Rocky release
Hi, The plugins are branchless and should stay so. Let us not dive into this madness again please. 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-dev] [releases][rocky][tempest-plugins][ptl] Reminder to tag the Tempest plugins for Rocky release
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. [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
