Re: [openstack-dev] Are we ready to put stable/ocata into extended maintenance mode?
On 9/21/2018 9:08 AM, Elõd Illés wrote: Hi, Here is an etherpad with the teams that have stable:follow-policy tag on their repos: https://etherpad.openstack.org/p/ocata-final-release-before-em On the links you can find reports about the open and unreleased changes, that could be a useful input for the before-EM/final release. Please have a look at the report (and review the open patches if there are) so that a release can be made if necessary. Thanks, Előd I've added nova's ocata-em tracking etherpad to the list. https://etherpad.openstack.org/p/nova-ocata-em -- Thanks, Matt __ 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] Are we ready to put stable/ocata into extended maintenance mode?
On Fri, Sep 21, 2018 at 08:26:41AM -0600, Doug Hellmann wrote: > Excerpts from Elõd Illés's message of 2018-09-21 16:08:28 +0200: > > Hi, > > > > Here is an etherpad with the teams that have stable:follow-policy tag on > > their repos: > > > > https://etherpad.openstack.org/p/ocata-final-release-before-em > > > > On the links you can find reports about the open and unreleased changes, > > that could be a useful input for the before-EM/final release. > > Please have a look at the report (and review the open patches if there > > are) so that a release can be made if necessary. > > > > Thanks, > > > > Előd > > Thanks for pulling all of this information together! > > Doug > Really useful information Előd - thanks for getting that put together! 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] Are we ready to put stable/ocata into extended maintenance mode?
Excerpts from Elõd Illés's message of 2018-09-21 16:08:28 +0200: > Hi, > > Here is an etherpad with the teams that have stable:follow-policy tag on > their repos: > > https://etherpad.openstack.org/p/ocata-final-release-before-em > > On the links you can find reports about the open and unreleased changes, > that could be a useful input for the before-EM/final release. > Please have a look at the report (and review the open patches if there > are) so that a release can be made if necessary. > > Thanks, > > Előd Thanks for pulling all of this information together! 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] Are we ready to put stable/ocata into extended maintenance mode?
Hi, Here is an etherpad with the teams that have stable:follow-policy tag on their repos: https://etherpad.openstack.org/p/ocata-final-release-before-em On the links you can find reports about the open and unreleased changes, that could be a useful input for the before-EM/final release. Please have a look at the report (and review the open patches if there are) so that a release can be made if necessary. Thanks, Előd On 2018-09-21 00:53, Matt Riedemann wrote: On 9/20/2018 12:08 PM, Elõd Illés wrote: Hi Matt, About 1.: I think it is a good idea to cut a final release (especially as some vendor/operator would be glad even if there would be some release in Extended Maintenance, too, what most probably won't happen...) -- saying that without knowing how much of a burden would it be for projects to do this final release... After that it sounds reasonably to tag the branches EM (as it is written in the mentioned resolution). Do you have any plan about how to coordinate the 'final releases' and do the EM-tagging? Thanks for raising these questions! Cheers, Előd For anyone following along and that cares about this (hopefully PTLs), Előd, Doug, Sean and I formulated a plan in IRC today [1]. [1] http://eavesdrop.openstack.org/irclogs/%23openstack-stable/%23openstack-stable.2018-09-20.log.html#t2018-09-20T17:10:56 __ 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] Are we ready to put stable/ocata into extended maintenance mode?
On 9/20/2018 12:08 PM, Elõd Illés wrote: Hi Matt, About 1.: I think it is a good idea to cut a final release (especially as some vendor/operator would be glad even if there would be some release in Extended Maintenance, too, what most probably won't happen...) -- saying that without knowing how much of a burden would it be for projects to do this final release... After that it sounds reasonably to tag the branches EM (as it is written in the mentioned resolution). Do you have any plan about how to coordinate the 'final releases' and do the EM-tagging? Thanks for raising these questions! Cheers, Előd For anyone following along and that cares about this (hopefully PTLs), Előd, Doug, Sean and I formulated a plan in IRC today [1]. [1] http://eavesdrop.openstack.org/irclogs/%23openstack-stable/%23openstack-stable.2018-09-20.log.html#t2018-09-20T17:10:56 -- Thanks, Matt __ 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] Are we ready to put stable/ocata into extended maintenance mode?
Hi Matt, About 1.: I think it is a good idea to cut a final release (especially as some vendor/operator would be glad even if there would be some release in Extended Maintenance, too, what most probably won't happen...) -- saying that without knowing how much of a burden would it be for projects to do this final release... After that it sounds reasonably to tag the branches EM (as it is written in the mentioned resolution). Do you have any plan about how to coordinate the 'final releases' and do the EM-tagging? Thanks for raising these questions! Cheers, Előd On 2018-09-18 21:27, Matt Riedemann wrote: The release page says Ocata is planned to go into extended maintenance mode on Aug 27 [1]. There really isn't much to this except it means we don't do releases for Ocata anymore [2]. There is a caveat that project teams that do not wish to maintain stable/ocata after this point can immediately end of life the branch for their project [3]. We can still run CI using tags, e.g. if keystone goes ocata-eol, devstack on stable/ocata can still continue to install from stable/ocata for nova and the ocata-eol tag for keystone. Having said that, if there is no undue burden on the project team keeping the lights on for stable/ocata, I would recommend not tagging the stable/ocata branch end of life at this point. So, questions that need answering are: 1. Should we cut a final release for projects with stable/ocata branches before going into extended maintenance mode? I tend to think "yes" to flush the queue of backports. In fact, [3] doesn't mention it, but the resolution said we'd tag the branch [4] to indicate it has entered the EM phase. 2. Are there any projects that would want to skip EM and go directly to EOL (yes this feels like a Monopoly question)? [1] https://releases.openstack.org/ [2] https://docs.openstack.org/project-team-guide/stable-branches.html#maintenance-phases [3] https://docs.openstack.org/project-team-guide/stable-branches.html#extended-maintenance [4] https://governance.openstack.org/tc/resolutions/20180301-stable-branch-eol.html#end-of-life __ 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] Are we ready to put stable/ocata into extended maintenance mode?
On Tue, Sep 18, 2018 at 1:27 PM, Matt Riedemann wrote: > The release page says Ocata is planned to go into extended maintenance mode > on Aug 27 [1]. There really isn't much to this except it means we don't do > releases for Ocata anymore [2]. There is a caveat that project teams that do > not wish to maintain stable/ocata after this point can immediately end of > life the branch for their project [3]. We can still run CI using tags, e.g. > if keystone goes ocata-eol, devstack on stable/ocata can still continue to > install from stable/ocata for nova and the ocata-eol tag for keystone. > Having said that, if there is no undue burden on the project team keeping > the lights on for stable/ocata, I would recommend not tagging the > stable/ocata branch end of life at this point. > > So, questions that need answering are: > > 1. Should we cut a final release for projects with stable/ocata branches > before going into extended maintenance mode? I tend to think "yes" to flush > the queue of backports. In fact, [3] doesn't mention it, but the resolution > said we'd tag the branch [4] to indicate it has entered the EM phase. > > 2. Are there any projects that would want to skip EM and go directly to EOL > (yes this feels like a Monopoly question)? > I believe TripleO would like to EOL instead of EM for Ocata as indicated by the thead http://lists.openstack.org/pipermail/openstack-dev/2018-September/134671.html Thanks, -Alex > [1] https://releases.openstack.org/ > [2] > https://docs.openstack.org/project-team-guide/stable-branches.html#maintenance-phases > [3] > https://docs.openstack.org/project-team-guide/stable-branches.html#extended-maintenance > [4] > https://governance.openstack.org/tc/resolutions/20180301-stable-branch-eol.html#end-of-life > > -- > > Thanks, > > Matt > > __ > 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] Are we ready to put stable/ocata into extended maintenance mode?
The release page says Ocata is planned to go into extended maintenance mode on Aug 27 [1]. There really isn't much to this except it means we don't do releases for Ocata anymore [2]. There is a caveat that project teams that do not wish to maintain stable/ocata after this point can immediately end of life the branch for their project [3]. We can still run CI using tags, e.g. if keystone goes ocata-eol, devstack on stable/ocata can still continue to install from stable/ocata for nova and the ocata-eol tag for keystone. Having said that, if there is no undue burden on the project team keeping the lights on for stable/ocata, I would recommend not tagging the stable/ocata branch end of life at this point. So, questions that need answering are: 1. Should we cut a final release for projects with stable/ocata branches before going into extended maintenance mode? I tend to think "yes" to flush the queue of backports. In fact, [3] doesn't mention it, but the resolution said we'd tag the branch [4] to indicate it has entered the EM phase. 2. Are there any projects that would want to skip EM and go directly to EOL (yes this feels like a Monopoly question)? [1] https://releases.openstack.org/ [2] https://docs.openstack.org/project-team-guide/stable-branches.html#maintenance-phases [3] https://docs.openstack.org/project-team-guide/stable-branches.html#extended-maintenance [4] https://governance.openstack.org/tc/resolutions/20180301-stable-branch-eol.html#end-of-life -- Thanks, Matt __ 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
