Re: [openstack-dev] [all][stable][ptls] Tagging liberty as EOL
On Tue, Dec 20, 2016 at 4:02 PM, Samuel Cassibawrote: > > > > On Dec 19, 2016, at 14:31, Tony Breeds wrote: > > > > On Mon, Dec 19, 2016 at 09:18:20AM -0800, Samuel Cassiba wrote: > > > >> The Chef OpenStack cookbooks team is way late to the party. The > cookbooks > >> (openstack/cookbook-openstack-*, openstack/openstack-chef-repo ) > should have > >> had their liberty branches EOL’d. I have checked and no open reviews > exist > >> against liberty. > > > > Thanks. > > > > While I have your attention what about your older branches. Is there any > > mertit keeping the kilo branches in openstack/cookbook-openstack-* or the > > stable/{grizzly,havana,icehouse,juno} branches in > openstack/openstack-chef-repo > > > > No, no merit in keeping older branches around. They can be rightfully > EOL’d as well. > Howdy, I've cleaned up all of these branches for you. The repos that have been retired haven't been touched. A lot of the repos had eol-$release tags but the format used for the rest of openstack is typically $release-eol which is the format I have kept for retiring kilo and liberty against. Let me know if you have any questions. Cheers, Josh > > Many thanks! > > > Yours Tony. > > > __ > > 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] [all][stable][ptls] Tagging liberty as EOL
On Mon, Dec 19, 2016 at 11:10 AM, Tony Breedswrote: > On Fri, Dec 16, 2016 at 05:41:31PM -0500, Emilien Macchi wrote: > > Hey Tony, > > > > Could we also EOL tripleo-incubator and tripleo-image-elements > > stable/icehouse please? > > Yup, No problem. > I have retired icehouse in both of those repos. Cheers, Josh > > Tony. > > __ > 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] [all][stable][ptls] Tagging liberty as EOL
> > On Dec 19, 2016, at 14:31, Tony Breedswrote: > > On Mon, Dec 19, 2016 at 09:18:20AM -0800, Samuel Cassiba wrote: > >> The Chef OpenStack cookbooks team is way late to the party. The cookbooks >> (openstack/cookbook-openstack-*, openstack/openstack-chef-repo ) should have >> had their liberty branches EOL’d. I have checked and no open reviews exist >> against liberty. > > Thanks. > > While I have your attention what about your older branches. Is there any > mertit keeping the kilo branches in openstack/cookbook-openstack-* or the > stable/{grizzly,havana,icehouse,juno} branches in > openstack/openstack-chef-repo > No, no merit in keeping older branches around. They can be rightfully EOL’d as well. Many thanks! > Yours Tony. > __ > 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 signature.asc Description: Message signed with OpenPGP using GPGMail __ 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] [all][stable][ptls] Tagging liberty as EOL
On Mon, Dec 19, 2016 at 09:18:20AM -0800, Samuel Cassiba wrote: > The Chef OpenStack cookbooks team is way late to the party. The cookbooks > (openstack/cookbook-openstack-*, openstack/openstack-chef-repo ) should have > had their liberty branches EOL’d. I have checked and no open reviews exist > against liberty. Thanks. While I have your attention what about your older branches. Is there any mertit keeping the kilo branches in openstack/cookbook-openstack-* or the stable/{grizzly,havana,icehouse,juno} branches in openstack/openstack-chef-repo Yours Tony. signature.asc Description: PGP signature __ 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] [all][stable][ptls] Tagging liberty as EOL
On Nov 21, 2016, at 18:35, Tony Breedswrote: > > Hi all, >I'm late in sending this announement, but I'm glad to see several projects > have already requested EOL releases to make it trivial and obvious where to > apply the tag. > > I'm proposing to EOL all projects that meet one or more of the following > criteria: > > - The project is openstack-dev/devstack, openstack-dev/grenade or > openstack/requirements > - The project has the 'check-requirements' job listed as a template in > project-config:zuul/layout.yaml > - The project gates with either devstack or grenade jobs > - The project is listed in governance:reference/projects.yaml and is tagged > with 'stable:follows-policy'. > > > Some statistics: > All Repos : 1493 (covered in zuul/layout.yaml) > Checked Repos : 406 (match one or more of the above > criteria) > Repos with liberty branches: 305 > EOL Repos : 171 (repos that match the criteria *and* > have > a liberty branch) [1] > NOT EOL Repos : 134 (repos with a liberty branch but > otherwise do not match) [2] > DSVM Repos (staying) : 68 (repos that use dsvm but don't have > liberty branches) > Open Reviews : 94 (reviews to close) > > > Please look over both lists by 2016-11-27 00:00 UTC and let me know if: > - A project is in list 1 and *really* *really* wants to opt *OUT* of EOLing > and > why. Note doing this will amost certainly reduce the testing coverage you > have in the gate. > - A project is in list 2 that would like to opt *IN* to tagging/EOLing > > Any projects that will be EOL'd will need all open reviews abandoned before it > can be processed. I'm very happy to do this, or if I don't have permissios to > do it ask a gerrit admin to do it. > > I'll batch the removal of the stable/liberty branches between Nov 28th and Dec > 3rd (UTC+1100). Then during Decemeber I'll attempt to cleanup > zuul/layout.yaml > to remove liberty exclusions and jobs. > > Yours Tony. > > [1] > https://gist.github.com/tbreeds/93cd346c37aa46269456f56649f0a4ac#file-liberty_eol_data-txt-L1 > [2] > https://gist.github.com/tbreeds/93cd346c37aa46269456f56649f0a4ac#file-liberty_eol_data-txt-L181 > __ > 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 The Chef OpenStack cookbooks team is way late to the party. The cookbooks (openstack/cookbook-openstack-*, openstack/openstack-chef-repo ) should have had their liberty branches EOL’d. I have checked and no open reviews exist against liberty. -- Best, Samuel Cassiba signature.asc Description: Message signed with OpenPGP using GPGMail __ 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] [all][stable][ptls] Tagging liberty as EOL
On Fri, Dec 16, 2016 at 05:41:31PM -0500, Emilien Macchi wrote: > Hey Tony, > > Could we also EOL tripleo-incubator and tripleo-image-elements > stable/icehouse please? Yup, No problem. Tony. signature.asc Description: PGP signature __ 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] [all][stable][ptls] Tagging liberty as EOL
Hey Tony, Could we also EOL tripleo-incubator and tripleo-image-elements stable/icehouse please? Thanks, On Mon, Nov 21, 2016 at 9:35 PM, Tony Breedswrote: > Hi all, > I'm late in sending this announement, but I'm glad to see several projects > have already requested EOL releases to make it trivial and obvious where to > apply the tag. > > I'm proposing to EOL all projects that meet one or more of the following > criteria: > > - The project is openstack-dev/devstack, openstack-dev/grenade or > openstack/requirements > - The project has the 'check-requirements' job listed as a template in > project-config:zuul/layout.yaml > - The project gates with either devstack or grenade jobs > - The project is listed in governance:reference/projects.yaml and is tagged > with 'stable:follows-policy'. > > > Some statistics: > All Repos : 1493 (covered in zuul/layout.yaml) > Checked Repos : 406 (match one or more of the above > criteria) > Repos with liberty branches: 305 > EOL Repos : 171 (repos that match the criteria *and* > have >a liberty branch) [1] > NOT EOL Repos : 134 (repos with a liberty branch but >otherwise do not match) [2] > DSVM Repos (staying) : 68 (repos that use dsvm but don't have >liberty branches) > Open Reviews : 94 (reviews to close) > > > Please look over both lists by 2016-11-27 00:00 UTC and let me know if: > - A project is in list 1 and *really* *really* wants to opt *OUT* of EOLing > and > why. Note doing this will amost certainly reduce the testing coverage you > have in the gate. > - A project is in list 2 that would like to opt *IN* to tagging/EOLing > > Any projects that will be EOL'd will need all open reviews abandoned before it > can be processed. I'm very happy to do this, or if I don't have permissios to > do it ask a gerrit admin to do it. > > I'll batch the removal of the stable/liberty branches between Nov 28th and Dec > 3rd (UTC+1100). Then during Decemeber I'll attempt to cleanup > zuul/layout.yaml > to remove liberty exclusions and jobs. > > Yours Tony. > > [1] > https://gist.github.com/tbreeds/93cd346c37aa46269456f56649f0a4ac#file-liberty_eol_data-txt-L1 > [2] > https://gist.github.com/tbreeds/93cd346c37aa46269456f56649f0a4ac#file-liberty_eol_data-txt-L181 > > __ > 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 > -- Emilien Macchi __ 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] [all][stable][ptls] Tagging liberty as EOL
On Tue, Nov 22, 2016 at 01:35:48PM +1100, Tony Breeds wrote: > I'll batch the removal of the stable/liberty branches between Nov 28th and Dec > 3rd (UTC+1100). Then during Decemeber I'll attempt to cleanup > zuul/layout.yaml > to remove liberty exclusions and jobs. This took longer as there are a few repos that are scheduled for EOL that were a little problematic during the kilo cycle. I've updated the list at [1] Can the infra team please run eol_branch.sh [2] over the repos listed at that URL [1] and flagged with 'Please EOL'. The others will need to be done later. eol_branch.sh needs just the repo names what can be generated with something like: URL=https://gist.githubusercontent.com/tbreeds/93cd346c37aa46269456f56649f0a4ac/raw/liberty_eol_data.txt eol_branch.sh REPOS=$(curl -s $URL | awk '/Please EOL/ {print $1}') The data format is a balance between human and machine readable. Yours Tony. [1] https://gist.github.com/tbreeds/93cd346c37aa46269456f56649f0a4ac#file-liberty_eol_data-txt [2] http://git.openstack.org/cgit/openstack-infra/release-tools/tree/eol_branch.sh signature.asc Description: PGP signature __ 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] [all][stable][ptls] Tagging liberty as EOL
On Tue, Nov 22, 2016 at 05:51:30PM -0700, Alex Schultz wrote: > On Tue, Nov 22, 2016 at 5:13 PM, Tony Breedswrote: > > On Tue, Nov 22, 2016 at 09:21:00AM -0700, Alex Schultz wrote: > > > >> For the puppet items on the second list[0], the liberty branches of > >> puppet-aodh and puppet-openstack_spec_helper can be EOL'ed. > > > > Thanks I updated the list. Can I ask why puppet-murano will be left behind? > > > > Because I got side tracked with barbican and forgot to include it in > the list. That can be EOL'ed as well. Ahh cool. Thanks. Yours Tony. signature.asc Description: PGP signature __ 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] [all][stable][ptls] Tagging liberty as EOL
On Tue, Nov 22, 2016 at 5:13 PM, Tony Breedswrote: > On Tue, Nov 22, 2016 at 09:21:00AM -0700, Alex Schultz wrote: > >> For the puppet items on the second list[0], the liberty branches of >> puppet-aodh and puppet-openstack_spec_helper can be EOL'ed. > > Thanks I updated the list. Can I ask why puppet-murano will be left behind? > Because I got side tracked with barbican and forgot to include it in the list. That can be EOL'ed as well. Thanks, -Alex >> I assume >> puppet-barbican is on that list because it doesn't have a >> stable/liberty branch since the first release was newton, so that's >> fine. > > Yup that sounds about right. > > Yours Tony. > > __ > 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] [all][stable][ptls] Tagging liberty as EOL
On Tue, Nov 22, 2016 at 12:14:30PM -0500, Emilien Macchi wrote: > In TripleO, we agreed to EOL Liberty for all projects, included those > in the second list: > openstack/instack-undercloud > openstack/tripleo-heat-templates tripleo > openstack/tripleo-puppet-elements Added and I've updated the lists. You can see the chnages at [1] Yours Tony. [1] but the nett effect is we're EOL'ing 5 more repos. signature.asc Description: PGP signature __ 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] [all][stable][ptls] Tagging liberty as EOL
On Tue, Nov 22, 2016 at 09:21:00AM -0700, Alex Schultz wrote: > For the puppet items on the second list[0], the liberty branches of > puppet-aodh and puppet-openstack_spec_helper can be EOL'ed. Thanks I updated the list. Can I ask why puppet-murano will be left behind? > I assume > puppet-barbican is on that list because it doesn't have a > stable/liberty branch since the first release was newton, so that's > fine. Yup that sounds about right. Yours Tony. signature.asc Description: PGP signature __ 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] [all][stable][ptls] Tagging liberty as EOL
Hey Tony, On Mon, Nov 21, 2016 at 9:35 PM, Tony Breedswrote: > Hi all, > I'm late in sending this announement, but I'm glad to see several projects > have already requested EOL releases to make it trivial and obvious where to > apply the tag. > > I'm proposing to EOL all projects that meet one or more of the following > criteria: > > - The project is openstack-dev/devstack, openstack-dev/grenade or > openstack/requirements > - The project has the 'check-requirements' job listed as a template in > project-config:zuul/layout.yaml > - The project gates with either devstack or grenade jobs > - The project is listed in governance:reference/projects.yaml and is tagged > with 'stable:follows-policy'. > > > Some statistics: > All Repos : 1493 (covered in zuul/layout.yaml) > Checked Repos : 406 (match one or more of the above > criteria) > Repos with liberty branches: 305 > EOL Repos : 171 (repos that match the criteria *and* > have >a liberty branch) [1] > NOT EOL Repos : 134 (repos with a liberty branch but >otherwise do not match) [2] > DSVM Repos (staying) : 68 (repos that use dsvm but don't have >liberty branches) > Open Reviews : 94 (reviews to close) > > > Please look over both lists by 2016-11-27 00:00 UTC and let me know if: > - A project is in list 1 and *really* *really* wants to opt *OUT* of EOLing > and > why. Note doing this will amost certainly reduce the testing coverage you > have in the gate. > - A project is in list 2 that would like to opt *IN* to tagging/EOLing > > Any projects that will be EOL'd will need all open reviews abandoned before it > can be processed. I'm very happy to do this, or if I don't have permissios to > do it ask a gerrit admin to do it. In TripleO, we agreed to EOL Liberty for all projects, included those in the second list: openstack/instack-undercloud openstack/tripleo-heat-templates tripleo openstack/tripleo-puppet-elements I'll make sure today that all open reviews are merged or abandoned. Please let me know if you need any help for tagging & zuul things. Thanks, > I'll batch the removal of the stable/liberty branches between Nov 28th and Dec > 3rd (UTC+1100). Then during Decemeber I'll attempt to cleanup > zuul/layout.yaml > to remove liberty exclusions and jobs. > > Yours Tony. > > [1] > https://gist.github.com/tbreeds/93cd346c37aa46269456f56649f0a4ac#file-liberty_eol_data-txt-L1 > [2] > https://gist.github.com/tbreeds/93cd346c37aa46269456f56649f0a4ac#file-liberty_eol_data-txt-L181 > > __ > 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 > -- Emilien Macchi __ 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] [all][stable][ptls] Tagging liberty as EOL
Hey Tony, On Mon, Nov 21, 2016 at 7:35 PM, Tony Breedswrote: > Hi all, > I'm late in sending this announement, but I'm glad to see several projects > have already requested EOL releases to make it trivial and obvious where to > apply the tag. > > I'm proposing to EOL all projects that meet one or more of the following > criteria: > > - The project is openstack-dev/devstack, openstack-dev/grenade or > openstack/requirements > - The project has the 'check-requirements' job listed as a template in > project-config:zuul/layout.yaml > - The project gates with either devstack or grenade jobs > - The project is listed in governance:reference/projects.yaml and is tagged > with 'stable:follows-policy'. > > > Some statistics: > All Repos : 1493 (covered in zuul/layout.yaml) > Checked Repos : 406 (match one or more of the above > criteria) > Repos with liberty branches: 305 > EOL Repos : 171 (repos that match the criteria *and* > have >a liberty branch) [1] > NOT EOL Repos : 134 (repos with a liberty branch but >otherwise do not match) [2] > DSVM Repos (staying) : 68 (repos that use dsvm but don't have >liberty branches) > Open Reviews : 94 (reviews to close) > > > Please look over both lists by 2016-11-27 00:00 UTC and let me know if: > - A project is in list 1 and *really* *really* wants to opt *OUT* of EOLing > and > why. Note doing this will amost certainly reduce the testing coverage you > have in the gate. > - A project is in list 2 that would like to opt *IN* to tagging/EOLing > For the puppet items on the second list[0], the liberty branches of puppet-aodh and puppet-openstack_spec_helper can be EOL'ed. I assume puppet-barbican is on that list because it doesn't have a stable/liberty branch since the first release was newton, so that's fine. Thanks, -Alex [0] https://gist.github.com/tbreeds/93cd346c37aa46269456f56649f0a4ac#file-liberty_eol_data-txt-L308-L310 > Any projects that will be EOL'd will need all open reviews abandoned before it > can be processed. I'm very happy to do this, or if I don't have permissios to > do it ask a gerrit admin to do it. > > I'll batch the removal of the stable/liberty branches between Nov 28th and Dec > 3rd (UTC+1100). Then during Decemeber I'll attempt to cleanup > zuul/layout.yaml > to remove liberty exclusions and jobs. > > Yours Tony. > > [1] > https://gist.github.com/tbreeds/93cd346c37aa46269456f56649f0a4ac#file-liberty_eol_data-txt-L1 > [2] > https://gist.github.com/tbreeds/93cd346c37aa46269456f56649f0a4ac#file-liberty_eol_data-txt-L181 > > __ > 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] [all][stable][ptls] Tagging liberty as EOL
Hi all, I'm late in sending this announement, but I'm glad to see several projects have already requested EOL releases to make it trivial and obvious where to apply the tag. I'm proposing to EOL all projects that meet one or more of the following criteria: - The project is openstack-dev/devstack, openstack-dev/grenade or openstack/requirements - The project has the 'check-requirements' job listed as a template in project-config:zuul/layout.yaml - The project gates with either devstack or grenade jobs - The project is listed in governance:reference/projects.yaml and is tagged with 'stable:follows-policy'. Some statistics: All Repos : 1493 (covered in zuul/layout.yaml) Checked Repos : 406 (match one or more of the above criteria) Repos with liberty branches: 305 EOL Repos : 171 (repos that match the criteria *and* have a liberty branch) [1] NOT EOL Repos : 134 (repos with a liberty branch but otherwise do not match) [2] DSVM Repos (staying) : 68 (repos that use dsvm but don't have liberty branches) Open Reviews : 94 (reviews to close) Please look over both lists by 2016-11-27 00:00 UTC and let me know if: - A project is in list 1 and *really* *really* wants to opt *OUT* of EOLing and why. Note doing this will amost certainly reduce the testing coverage you have in the gate. - A project is in list 2 that would like to opt *IN* to tagging/EOLing Any projects that will be EOL'd will need all open reviews abandoned before it can be processed. I'm very happy to do this, or if I don't have permissios to do it ask a gerrit admin to do it. I'll batch the removal of the stable/liberty branches between Nov 28th and Dec 3rd (UTC+1100). Then during Decemeber I'll attempt to cleanup zuul/layout.yaml to remove liberty exclusions and jobs. Yours Tony. [1] https://gist.github.com/tbreeds/93cd346c37aa46269456f56649f0a4ac#file-liberty_eol_data-txt-L1 [2] https://gist.github.com/tbreeds/93cd346c37aa46269456f56649f0a4ac#file-liberty_eol_data-txt-L181 signature.asc Description: PGP signature __ 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