Re: [openstack-dev] [stable][all] Tagging kilo-eol for "the world"
Hey Jesse, Sorry for the delay. I've gone ahead and removed icehouse, juno and kilo branches creating tags in their places. Cheers, Josh On Wed, Jul 6, 2016 at 3:27 AM, Jesse Pretorius < jesse.pretor...@rackspace.co.uk> wrote: > From: Joshua Hesketh > > > I assume you want to wait for the tag to merge before removing the branch? > > The only tag job I can see for openstack-ansible* projects is the > releasenotes one. This should be harmless as it just generates the notes > for mitaka and liberty branches. I'm going to hold off until the final tag > has merged anyway if you want to confirm this first. > > > Thanks Josh – The final Kilo tag has merged so we’re good to go. We’re > happy to also go straight ahead with the eol tags for the icehouse and juno > branches too. > > -- > Rackspace Limited is a company registered in England & Wales (company > registered number 03897010) whose registered office is at 5 Millington > Road, Hyde Park Hayes, Middlesex UB3 4AZ. Rackspace Limited privacy policy > can be viewed at www.rackspace.co.uk/legal/privacy-policy - This e-mail > message may contain confidential or privileged information intended for the > recipient. Any dissemination, distribution or copying of the enclosed > material is prohibited. If you receive this transmission in error, please > notify us immediately by e-mail at ab...@rackspace.com and delete the > original message. Your cooperation is appreciated. > > __ > 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] [stable][all] Tagging kilo-eol for "the world"
From: Joshua Hesketh mailto:joshua.hesk...@gmail.com>> I assume you want to wait for the tag to merge before removing the branch? The only tag job I can see for openstack-ansible* projects is the releasenotes one. This should be harmless as it just generates the notes for mitaka and liberty branches. I'm going to hold off until the final tag has merged anyway if you want to confirm this first. Thanks Josh – The final Kilo tag has merged so we’re good to go. We’re happy to also go straight ahead with the eol tags for the icehouse and juno branches too. Rackspace Limited is a company registered in England & Wales (company registered number 03897010) whose registered office is at 5 Millington Road, Hyde Park Hayes, Middlesex UB3 4AZ. Rackspace Limited privacy policy can be viewed at www.rackspace.co.uk/legal/privacy-policy - This e-mail message may contain confidential or privileged information intended for the recipient. Any dissemination, distribution or copying of the enclosed material is prohibited. If you receive this transmission in error, please notify us immediately by e-mail at ab...@rackspace.com and delete the original message. Your cooperation is appreciated. __ 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] [stable][all] Tagging kilo-eol for "the world"
On Fri, Jul 1, 2016 at 9:26 PM, Jesse Pretorius < jesse.pretor...@rackspace.co.uk> wrote: > Hi all, > > Now that OpenStack-Ansible has the final Swift kilo-eol tag implemented > we’ve requested a final tag [1]. Once that merges we are ready to have our > kilo-eol tag implemented and the ‘kilo’ branch removed. > I assume you want to wait for the tag to merge before removing the branch? > > Just to make life interesting, we still have leftover ‘juno’ and > ‘icehouse’ branches and would like to implement eol tags for them too. I > think we have the appropriate skips in place for the juno branch so there > should be no funky post-tag jobs kicking off for them, but the icehouse > branch may end up with some unknown jobs kicking off. If you can help > identify the changes we need to get implemented into project-config then we > can be rid of the old cruft. > The only tag job I can see for openstack-ansible* projects is the releasenotes one. This should be harmless as it just generates the notes for mitaka and liberty branches. I'm going to hold off until the final tag has merged anyway if you want to confirm this first. Cheers, Josh > Thanks, > > Jesse > > -- > Rackspace Limited is a company registered in England & Wales (company > registered number 03897010) whose registered office is at 5 Millington > Road, Hyde Park Hayes, Middlesex UB3 4AZ. Rackspace Limited privacy policy > can be viewed at www.rackspace.co.uk/legal/privacy-policy - This e-mail > message may contain confidential or privileged information intended for the > recipient. Any dissemination, distribution or copying of the enclosed > material is prohibited. If you receive this transmission in error, please > notify us immediately by e-mail at ab...@rackspace.com and delete the > original message. Your cooperation is appreciated. > > __ > 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] [stable][all] Tagging kilo-eol for "the world"
Now that OpenStack-Ansible has the final Swift kilo-eol tag implemented we’ve requested a final tag [1]. Once that merges we are ready to have our kilo-eol tag implemented and the ‘kilo’ branch removed. Whoops – I forget to add the link to the final Kilo tag request. [1] https://review.openstack.org/336505 Rackspace Limited is a company registered in England & Wales (company registered number 03897010) whose registered office is at 5 Millington Road, Hyde Park Hayes, Middlesex UB3 4AZ. Rackspace Limited privacy policy can be viewed at www.rackspace.co.uk/legal/privacy-policy - This e-mail message may contain confidential or privileged information intended for the recipient. Any dissemination, distribution or copying of the enclosed material is prohibited. If you receive this transmission in error, please notify us immediately by e-mail at ab...@rackspace.com and delete the original message. Your cooperation is appreciated. __ 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] [stable][all] Tagging kilo-eol for "the world"
Hi all, Now that OpenStack-Ansible has the final Swift kilo-eol tag implemented we’ve requested a final tag [1]. Once that merges we are ready to have our kilo-eol tag implemented and the ‘kilo’ branch removed. Just to make life interesting, we still have leftover ‘juno’ and ‘icehouse’ branches and would like to implement eol tags for them too. I think we have the appropriate skips in place for the juno branch so there should be no funky post-tag jobs kicking off for them, but the icehouse branch may end up with some unknown jobs kicking off. If you can help identify the changes we need to get implemented into project-config then we can be rid of the old cruft. Thanks, Jesse Rackspace Limited is a company registered in England & Wales (company registered number 03897010) whose registered office is at 5 Millington Road, Hyde Park Hayes, Middlesex UB3 4AZ. Rackspace Limited privacy policy can be viewed at www.rackspace.co.uk/legal/privacy-policy - This e-mail message may contain confidential or privileged information intended for the recipient. Any dissemination, distribution or copying of the enclosed material is prohibited. If you receive this transmission in error, please notify us immediately by e-mail at ab...@rackspace.com and delete the original message. Your cooperation is appreciated. __ 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] [stable][all] Tagging kilo-eol for "the world"
On Sat, Jun 25, 2016 at 10:44 AM, Robert Collins wrote: > Removing the pbr branch should be fine - it was an exceptional thing > to have that branch in the first place - pbr is consumed by releases > only, and due to its place in the dependency graph is very very very > hard to pin or cap. > Based off this I have removed the stable/kilo branch from pbr. Cheers, Josh > > -Rob > > On 25 June 2016 at 12:37, Tony Breeds wrote: > > On Fri, Jun 24, 2016 at 04:36:03PM -0700, Sumit Naiksatam wrote: > >> Hi Tony, Thanks for your response, and no worries! We can live with > >> the kilo-eol tag, no need to try to delete it. And as you suggested, > >> we can add a second eol tag when we actually EoL this branch. > >> > >> As regards reviving the deleted branches, would a bug have to be > >> created somewhere to track this, or is this already on the radar of > >> the infra team (thanks in advance if it already is)? > > > > No bug needed. I'll work with the infra team to re-create the branch. > Just as > > a level set it wont be this weekend. > > > > 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] [stable][all] Tagging kilo-eol for "the world"
On Sat, Jun 25, 2016 at 4:20 AM, Sumit Naiksatam
wrote:
> Hi, I had earlier requested in this thread that the stable/kilo branch
> for the following repos be not deleted:
>
> > openstack/group-based-policy
> > openstack/group-based-policy-automation
> > openstack/group-based-policy-ui
> > openstack/python-group-based-policy-client
>
Hello,
Very sorry that these were removed. I should have checked this thread
closer.
I have recreated stable/kilo branches for each of those projects.
As Tony mentioned, due to the nature of the tags removing those is slightly
more complicated. We can remove them from the git farm upstream but those
who have already fetched the tags will need to manually remove them
locally. And if you do a subsequent (identical in name) kilo-eol tag only
those who had removed the incorrect version locally will fetch down the new
copy. In other words it'll be very easy for what you have tagged as
kilo-eol upstream to become different to what people may have in their
local copy.
As such, if you ever retire the branch it's probably important to name your
kilo-eol tag differently. If you call it something else there's no harm in
removing the kilo-eol upstream to keep it tidy if you so wish (let me know
if you need help with that).
Cheers,
Josh
>
> and the request was ack’ed by Tony (also in this thread). However, I
> just noticed that these branches have been deleted. Can this deletion
> please be reversed?
>
> Thanks,
> ~Sumit.
>
> On Fri, Jun 24, 2016 at 10:32 AM, Andreas Jaeger wrote:
> > On 06/24/2016 02:09 PM, Joshua Hesketh wrote:
> >>
> >> Hi all,
> >>
> >> I have completed removing stable/kilo branches from the projects listed
> >> [0]*. There are now 'kilo-eol' tags in place at the sha's where the
> >> branches were.
> >>
> >> *There are a couple of exceptions. oslo-incubator was listed but is an
> >> unmaintained project so no further action was required. Tony and I have
> >> also decided to hold off
> >> on openstack-dev/devstack, openstack-dev/grenade, openstack-dev/pbr
> >> and openstack/requirements until we are confident removing the
> >> stable/kilo branch will have no negative effects on the projects who
> >> opt-ed out of being EOL'd.
> >>
> >> In this process we noted a couple of repositories still have branches
> >> from Juno and even earlier. I haven't put together a comprehensive list
> >> of old branches, but rather if your project has an outdated branch that
> >> you would like removed and/or tagged as end-of-life, please let me know.
> >>
> >> For those interested in the script I used or other infra cores looking
> >> to perform this next time, it is up for review in the release-tools
> >> repo: https://review.openstack.org/333875
> >
> >
> > Thanks, Joshua.
> >
> > We're now removing the special handling of kilo branches from
> project-config
> > as well - it looks odd for some projects where kilo is removed from
> > conditions and we still have icehouse or juno. Followup changes are
> welcome.
> >
> > https://review.openstack.org/334008
> > https://review.openstack.org/333910
> > https://review.openstack.org/333977
> >
> > Andreas
> > --
> > Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
> > SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
> >GF: Felix Imendörffer, Jane Smithard, Graham Norton,
> >HRB 21284 (AG Nürnberg)
> > GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
> >
> >
> >
> >
> __
> > 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] [stable][all] Tagging kilo-eol for "the world"
On Sat, Jun 25, 2016 at 4:20 AM, Sumit Naiksatam
wrote:
> Hi, I had earlier requested in this thread that the stable/kilo branch
> for the following repos be not deleted:
>
> > openstack/group-based-policy
> > openstack/group-based-policy-automation
> > openstack/group-based-policy-ui
> > openstack/python-group-based-policy-client
>
> and the request was ack’ed by Tony (also in this thread). However, I
> just noticed that these branches have been deleted. Can this deletion
> please be reversed?
>
> Thanks,
> ~Sumit.
>
> On Fri, Jun 24, 2016 at 10:32 AM, Andreas Jaeger wrote:
> > On 06/24/2016 02:09 PM, Joshua Hesketh wrote:
> >>
> >> Hi all,
> >>
> >> I have completed removing stable/kilo branches from the projects listed
> >> [0]*. There are now 'kilo-eol' tags in place at the sha's where the
> >> branches were.
> >>
> >> *There are a couple of exceptions. oslo-incubator was listed but is an
> >> unmaintained project so no further action was required. Tony and I have
> >> also decided to hold off
> >> on openstack-dev/devstack, openstack-dev/grenade, openstack-dev/pbr
> >> and openstack/requirements until we are confident removing the
> >> stable/kilo branch will have no negative effects on the projects who
> >> opt-ed out of being EOL'd.
> >>
> >> In this process we noted a couple of repositories still have branches
> >> from Juno and even earlier. I haven't put together a comprehensive list
> >> of old branches, but rather if your project has an outdated branch that
> >> you would like removed and/or tagged as end-of-life, please let me know.
> >>
> >> For those interested in the script I used or other infra cores looking
> >> to perform this next time, it is up for review in the release-tools
> >> repo: https://review.openstack.org/333875
> >
> >
> > Thanks, Joshua.
> >
> > We're now removing the special handling of kilo branches from
> project-config
> > as well - it looks odd for some projects where kilo is removed from
> > conditions and we still have icehouse or juno. Followup changes are
> welcome.
> >
> > https://review.openstack.org/334008
> > https://review.openstack.org/333910
> > https://review.openstack.org/333977
> >
> > Andreas
> > --
> > Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
> > SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
> >GF: Felix Imendörffer, Jane Smithard, Graham Norton,
> >HRB 21284 (AG Nürnberg)
> > GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
> >
> >
> >
> >
> __
> > 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] [stable][all] Tagging kilo-eol for "the world"
Removing the pbr branch should be fine - it was an exceptional thing to have that branch in the first place - pbr is consumed by releases only, and due to its place in the dependency graph is very very very hard to pin or cap. -Rob On 25 June 2016 at 12:37, Tony Breeds wrote: > On Fri, Jun 24, 2016 at 04:36:03PM -0700, Sumit Naiksatam wrote: >> Hi Tony, Thanks for your response, and no worries! We can live with >> the kilo-eol tag, no need to try to delete it. And as you suggested, >> we can add a second eol tag when we actually EoL this branch. >> >> As regards reviving the deleted branches, would a bug have to be >> created somewhere to track this, or is this already on the radar of >> the infra team (thanks in advance if it already is)? > > No bug needed. I'll work with the infra team to re-create the branch. Just > as > a level set it wont be this weekend. > > 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] [stable][all] Tagging kilo-eol for "the world"
On Fri, Jun 24, 2016 at 04:36:03PM -0700, Sumit Naiksatam wrote: > Hi Tony, Thanks for your response, and no worries! We can live with > the kilo-eol tag, no need to try to delete it. And as you suggested, > we can add a second eol tag when we actually EoL this branch. > > As regards reviving the deleted branches, would a bug have to be > created somewhere to track this, or is this already on the radar of > the infra team (thanks in advance if it already is)? No bug needed. I'll work with the infra team to re-create the branch. Just as a level set it wont be this weekend. 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] [stable][all] Tagging kilo-eol for "the world"
Hi Tony, Thanks for your response, and no worries! We can live with the kilo-eol tag, no need to try to delete it. And as you suggested, we can add a second eol tag when we actually EoL this branch. As regards reviving the deleted branches, would a bug have to be created somewhere to track this, or is this already on the radar of the infra team (thanks in advance if it already is)? ~Sumit. On Fri, Jun 24, 2016 at 4:17 PM, Tony Breeds wrote: > On Fri, Jun 24, 2016 at 11:20:12AM -0700, Sumit Naiksatam wrote: >> Hi, I had earlier requested in this thread that the stable/kilo branch >> for the following repos be not deleted: >> >> > openstack/group-based-policy >> > openstack/group-based-policy-automation >> > openstack/group-based-policy-ui >> > openstack/python-group-based-policy-client >> >> and the request was ack’ed by Tony (also in this thread). However, I >> just noticed that these branches have been deleted. Can this deletion >> please be reversed? > > Firstly I appologise. I clearly gave Josh the wrong list of repos, which > included the repos above. > > I'm sure we can re-create the branch from the SHA and that *should* allow > development to continue hhowever due to the ditributed nature of gut deleteing > the tag is "hard". What this means in practise is that when you do decide to > dop the kilo branch you'll end up with a kilo-eol-for-real-this-time :) or > similar tag. > > Again I'm sorry fo the mistake. > > 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] [stable][all] Tagging kilo-eol for "the world"
On Fri, Jun 24, 2016 at 11:20:12AM -0700, Sumit Naiksatam wrote: > Hi, I had earlier requested in this thread that the stable/kilo branch > for the following repos be not deleted: > > > openstack/group-based-policy > > openstack/group-based-policy-automation > > openstack/group-based-policy-ui > > openstack/python-group-based-policy-client > > and the request was ack’ed by Tony (also in this thread). However, I > just noticed that these branches have been deleted. Can this deletion > please be reversed? Firstly I appologise. I clearly gave Josh the wrong list of repos, which included the repos above. I'm sure we can re-create the branch from the SHA and that *should* allow development to continue hhowever due to the ditributed nature of gut deleteing the tag is "hard". What this means in practise is that when you do decide to dop the kilo branch you'll end up with a kilo-eol-for-real-this-time :) or similar tag. Again I'm sorry fo the mistake. 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] [stable][all] Tagging kilo-eol for "the world"
Hi, I had earlier requested in this thread that the stable/kilo branch
for the following repos be not deleted:
> openstack/group-based-policy
> openstack/group-based-policy-automation
> openstack/group-based-policy-ui
> openstack/python-group-based-policy-client
and the request was ack’ed by Tony (also in this thread). However, I
just noticed that these branches have been deleted. Can this deletion
please be reversed?
Thanks,
~Sumit.
On Fri, Jun 24, 2016 at 10:32 AM, Andreas Jaeger wrote:
> On 06/24/2016 02:09 PM, Joshua Hesketh wrote:
>>
>> Hi all,
>>
>> I have completed removing stable/kilo branches from the projects listed
>> [0]*. There are now 'kilo-eol' tags in place at the sha's where the
>> branches were.
>>
>> *There are a couple of exceptions. oslo-incubator was listed but is an
>> unmaintained project so no further action was required. Tony and I have
>> also decided to hold off
>> on openstack-dev/devstack, openstack-dev/grenade, openstack-dev/pbr
>> and openstack/requirements until we are confident removing the
>> stable/kilo branch will have no negative effects on the projects who
>> opt-ed out of being EOL'd.
>>
>> In this process we noted a couple of repositories still have branches
>> from Juno and even earlier. I haven't put together a comprehensive list
>> of old branches, but rather if your project has an outdated branch that
>> you would like removed and/or tagged as end-of-life, please let me know.
>>
>> For those interested in the script I used or other infra cores looking
>> to perform this next time, it is up for review in the release-tools
>> repo: https://review.openstack.org/333875
>
>
> Thanks, Joshua.
>
> We're now removing the special handling of kilo branches from project-config
> as well - it looks odd for some projects where kilo is removed from
> conditions and we still have icehouse or juno. Followup changes are welcome.
>
> https://review.openstack.org/334008
> https://review.openstack.org/333910
> https://review.openstack.org/333977
>
> Andreas
> --
> Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
> SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
>GF: Felix Imendörffer, Jane Smithard, Graham Norton,
>HRB 21284 (AG Nürnberg)
> GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
>
>
>
> __
> 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] [stable][all] Tagging kilo-eol for "the world"
On 06/24/2016 02:09 PM, Joshua Hesketh wrote:
Hi all,
I have completed removing stable/kilo branches from the projects listed
[0]*. There are now 'kilo-eol' tags in place at the sha's where the
branches were.
*There are a couple of exceptions. oslo-incubator was listed but is an
unmaintained project so no further action was required. Tony and I have
also decided to hold off
on openstack-dev/devstack, openstack-dev/grenade, openstack-dev/pbr
and openstack/requirements until we are confident removing the
stable/kilo branch will have no negative effects on the projects who
opt-ed out of being EOL'd.
In this process we noted a couple of repositories still have branches
from Juno and even earlier. I haven't put together a comprehensive list
of old branches, but rather if your project has an outdated branch that
you would like removed and/or tagged as end-of-life, please let me know.
For those interested in the script I used or other infra cores looking
to perform this next time, it is up for review in the release-tools
repo: https://review.openstack.org/333875
Thanks, Joshua.
We're now removing the special handling of kilo branches from
project-config as well - it looks odd for some projects where kilo is
removed from conditions and we still have icehouse or juno. Followup
changes are welcome.
https://review.openstack.org/334008
https://review.openstack.org/333910
https://review.openstack.org/333977
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
__
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] [stable][all] Tagging kilo-eol for "the world"
Hi all, I have completed removing stable/kilo branches from the projects listed [0]*. There are now 'kilo-eol' tags in place at the sha's where the branches were. *There are a couple of exceptions. oslo-incubator was listed but is an unmaintained project so no further action was required. Tony and I have also decided to hold off on openstack-dev/devstack, openstack-dev/grenade, openstack-dev/pbr and openstack/requirements until we are confident removing the stable/kilo branch will have no negative effects on the projects who opt-ed out of being EOL'd. In this process we noted a couple of repositories still have branches from Juno and even earlier. I haven't put together a comprehensive list of old branches, but rather if your project has an outdated branch that you would like removed and/or tagged as end-of-life, please let me know. For those interested in the script I used or other infra cores looking to perform this next time, it is up for review in the release-tools repo: https://review.openstack.org/333875 Cheers, Josh [0] https://gist.github.com/tbreeds/7de812a5d363fab4bd425beae5084c87 On Sat, Jun 11, 2016 at 12:41 AM, Boden Russell wrote: > On 6/2/16 4:31 AM, Tony Breeds wrote: > > Any projects that will be EOL'd will need all open reviews abandoned > before it > > can be processed. > > openstack/vmware-nsx kilo patches have been abandoned in preparation for > the EOL. > > Thanks > > __ > 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] [stable][all] Tagging kilo-eol for "the world"
On 6/2/16 4:31 AM, Tony Breeds wrote: > Any projects that will be EOL'd will need all open reviews abandoned before it > can be processed. openstack/vmware-nsx kilo patches have been abandoned in preparation for the EOL. Thanks __ 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] [stable][all] Tagging kilo-eol for "the world"
On Thu, Jun 09, 2016 at 02:16:10AM -0700, Sumit Naiksatam wrote: > Hi Tony, The following repos should not be included in the EoL list since > they will not be EoL'ed at this time: > openstack/group-based-policy > openstack/group-based-policy-automation > openstack/group-based-policy-ui > openstack/python-group-based-policy-client Sure. I think it's a bad idea, and means we eaither need to tweak devstack-gate to handle this base or you need to drop all but the unit tests from your check and gate pipelines. 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] [stable][all] Tagging kilo-eol for "the world"
On Thu, Jun 9, 2016 at 3:10 PM, Ihar Hrachyshka wrote: > >> On 10 Jun 2016, at 00:03, Sumit Naiksatam wrote: >> >> On Thu, Jun 9, 2016 at 2:26 AM, Ihar Hrachyshka wrote: >>> On 09 Jun 2016, at 11:16, Sumit Naiksatam wrote: Hi Tony, The following repos should not be included in the EoL list since they will not be EoL'ed at this time: openstack/group-based-policy openstack/group-based-policy-automation openstack/group-based-policy-ui openstack/python-group-based-policy-client >>> >>> Would you mind clarifying why you absolutely need to maintain those old >>> branches for those projects, and how do you plan to do it if no tempest >>> jobs will be able to install other components for you? >>> >> >> We are continuing to fix bugs for kilo users. > > How are you supposed to validate that those fixes don’t break interactions > with other components? > We expect that any such fixes will be fairly contained, and well covered by the UTs. In addition we will be doing our due diligence with offline integration testing. > Ihar > __ > 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] [stable][all] Tagging kilo-eol for "the world"
> On 10 Jun 2016, at 00:03, Sumit Naiksatam wrote: > > On Thu, Jun 9, 2016 at 2:26 AM, Ihar Hrachyshka wrote: >> >>> On 09 Jun 2016, at 11:16, Sumit Naiksatam wrote: >>> >>> Hi Tony, The following repos should not be included in the EoL list since >>> they will not be EoL'ed at this time: >>> openstack/group-based-policy >>> openstack/group-based-policy-automation >>> openstack/group-based-policy-ui >>> openstack/python-group-based-policy-client >> >> Would you mind clarifying why you absolutely need to maintain those old >> branches for those projects, and how do you plan to do it if no tempest jobs >> will be able to install other components for you? >> > > We are continuing to fix bugs for kilo users. How are you supposed to validate that those fixes don’t break interactions with other components? Ihar __ 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] [stable][all] Tagging kilo-eol for "the world"
On Thu, Jun 9, 2016 at 2:26 AM, Ihar Hrachyshka wrote: > >> On 09 Jun 2016, at 11:16, Sumit Naiksatam wrote: >> >> Hi Tony, The following repos should not be included in the EoL list since >> they will not be EoL'ed at this time: >> openstack/group-based-policy >> openstack/group-based-policy-automation >> openstack/group-based-policy-ui >> openstack/python-group-based-policy-client > > Would you mind clarifying why you absolutely need to maintain those old > branches for those projects, and how do you plan to do it if no tempest jobs > will be able to install other components for you? > We are continuing to fix bugs for kilo users. > Ihar > __ > 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] [stable][all] Tagging kilo-eol for "the world"
> On 09 Jun 2016, at 11:16, Sumit Naiksatam wrote: > > Hi Tony, The following repos should not be included in the EoL list since > they will not be EoL'ed at this time: > openstack/group-based-policy > openstack/group-based-policy-automation > openstack/group-based-policy-ui > openstack/python-group-based-policy-client Would you mind clarifying why you absolutely need to maintain those old branches for those projects, and how do you plan to do it if no tempest jobs will be able to install other components for you? Ihar __ 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] [stable][all] Tagging kilo-eol for "the world"
Hi Tony, The following repos should not be included in the EoL list since they will not be EoL'ed at this time: openstack/group-based-policy openstack/group-based-policy-automation openstack/group-based-policy-ui openstack/python-group-based-policy-client Thanks, Sumit. On Jun 9, 2016 12:16 AM, "Tony Breeds" wrote: > On Fri, Jun 03, 2016 at 04:25:01PM +1000, Tony Breeds wrote: > > On Thu, Jun 02, 2016 at 08:31:43PM +1000, Tony Breeds wrote: > > > Hi all, > > > In early May we tagged/EOL'd several (13) projects. We'd like to > do a > > > final round for a more complete set. We looked for projects 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 is listed in governance:reference/projects.yaml and is > tagged > > > with 'release:managed' or 'stable:follows-policy' (or both). > > > > So We've had a few people opt into EOL'ing which is great. > > > > I've Moved the lists from paste.o.o to a gist. The reason for that is I > can > > update them, the URL doesn't change and there is a revision history (or > sorts). > > > > The 2 lists are now at: > https://gist.github.com/tbreeds/7de812a5d363fab4bd425beae5084c87 > > I have just re-generated the stats for open changes. The details are at: > https://gist.github.com/tbreeds/7de812a5d363fab4bd425beae5084c87 > > The summary looks like: > All Repos : 1007 > Checked Repos : 318 > Repos with kilo branches : 172 > EOL Repos : 152 > NOT EOL Repos : 20 > Tagged Repos : 15 > Open Reviews : 48 > > I have abandoned about half of the 48 reviews above but the rest I don't > have > permission to abandon. > > The remaining reviews are at: http://tiny.cc/os-kilo-still-open > > The repos below have been left open: > Open > Repo Project Reviews > Notes > --- --- > - > openstack/cookbook-openstack-bare-metal Chef OpenStack > openstack/cookbook-openstack-block-storageChef OpenStack > openstack/cookbook-openstack-client Chef OpenStack > openstack/cookbook-openstack-common Chef OpenStack > openstack/cookbook-openstack-compute Chef OpenStack > openstack/cookbook-openstack-dashboardChef OpenStack > openstack/cookbook-openstack-data-processing Chef OpenStack > openstack/cookbook-openstack-database Chef OpenStack > openstack/cookbook-openstack-identity Chef OpenStack > openstack/cookbook-openstack-imageChef OpenStack > openstack/cookbook-openstack-integration-test Chef OpenStack > openstack/cookbook-openstack-network Chef OpenStack > openstack/cookbook-openstack-object-storage Chef OpenStack > openstack/cookbook-openstack-ops-database Chef OpenStack > openstack/cookbook-openstack-ops-messagingChef OpenStack > openstack/cookbook-openstack-orchestrationChef OpenStack > openstack/cookbook-openstack-telemetryChef OpenStack > openstack/murano-apps murano 3 > openstack/openstack-ansible OpenStackAnsible > openstack/packstack BigTent > > 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] [stable][all] Tagging kilo-eol for "the world"
On Fri, Jun 03, 2016 at 04:25:01PM +1000, Tony Breeds wrote: > On Thu, Jun 02, 2016 at 08:31:43PM +1000, Tony Breeds wrote: > > Hi all, > > In early May we tagged/EOL'd several (13) projects. We'd like to do a > > final round for a more complete set. We looked for projects 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 is listed in governance:reference/projects.yaml and is tagged > > with 'release:managed' or 'stable:follows-policy' (or both). > > So We've had a few people opt into EOL'ing which is great. > > I've Moved the lists from paste.o.o to a gist. The reason for that is I can > update them, the URL doesn't change and there is a revision history (or > sorts). > > The 2 lists are now at: > https://gist.github.com/tbreeds/7de812a5d363fab4bd425beae5084c87 I have just re-generated the stats for open changes. The details are at: https://gist.github.com/tbreeds/7de812a5d363fab4bd425beae5084c87 The summary looks like: All Repos : 1007 Checked Repos : 318 Repos with kilo branches : 172 EOL Repos : 152 NOT EOL Repos : 20 Tagged Repos : 15 Open Reviews : 48 I have abandoned about half of the 48 reviews above but the rest I don't have permission to abandon. The remaining reviews are at: http://tiny.cc/os-kilo-still-open The repos below have been left open: Open Repo Project Reviews Notes --- --- - openstack/cookbook-openstack-bare-metal Chef OpenStack openstack/cookbook-openstack-block-storageChef OpenStack openstack/cookbook-openstack-client Chef OpenStack openstack/cookbook-openstack-common Chef OpenStack openstack/cookbook-openstack-compute Chef OpenStack openstack/cookbook-openstack-dashboardChef OpenStack openstack/cookbook-openstack-data-processing Chef OpenStack openstack/cookbook-openstack-database Chef OpenStack openstack/cookbook-openstack-identity Chef OpenStack openstack/cookbook-openstack-imageChef OpenStack openstack/cookbook-openstack-integration-test Chef OpenStack openstack/cookbook-openstack-network Chef OpenStack openstack/cookbook-openstack-object-storage Chef OpenStack openstack/cookbook-openstack-ops-database Chef OpenStack openstack/cookbook-openstack-ops-messagingChef OpenStack openstack/cookbook-openstack-orchestrationChef OpenStack openstack/cookbook-openstack-telemetryChef OpenStack openstack/murano-apps murano 3 openstack/openstack-ansible OpenStackAnsible openstack/packstack BigTent 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] [stable][all] Tagging kilo-eol for "the world"
Regarding openstack/murano-apps, in this repo we use stable/kilo branch not as a version of the apps, but rather than compatibility version of the app. Applications which are published in this branch are compatible with Murano from stable/kilo, given than we have a lag between upstream release and which release actually our users use and more over develop applications I would considered leaving stable/kilo branch in the openstack/murano-apps. On Mon, Jun 6, 2016 at 8:30 AM, Kirill Zaitsev wrote: > I’ve submitted a request to release all the unreleased code we still have > for murano repositories https://review.openstack.org/#/c/325359/ ; It would > be really great if we could get one final release before EOL’ing kilo in > murano, murano-dashboard, murano-agent and python-muranoclient, if that is > possible. After that I believe kilo branches in those repos are ready to be > EOL’ed and deleted. > > -- > Kirill Zaitsev > Software Engineer > Mirantis, Inc > > On 3 June 2016 at 09:26:58, Tony Breeds (t...@bakeyournoodle.com) wrote: > > On Thu, Jun 02, 2016 at 08:31:43PM +1000, Tony Breeds wrote: >> Hi all, >> In early May we tagged/EOL'd several (13) projects. We'd like to do a >> final round for a more complete set. We looked for projects 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 is listed in governance:reference/projects.yaml and is >> tagged >> with 'release:managed' or 'stable:follows-policy' (or both). > > So We've had a few people opt into EOL'ing which is great. > > I've Moved the lists from paste.o.o to a gist. The reason for that is I can > update them, the URL doesn't change and there is a revision history (or > sorts). > > The 2 lists are now at: > https://gist.github.com/tbreeds/7de812a5d363fab4bd425beae5084c87 > > Given that there are now only 39 repos that are not (yet) EOL'ing I'm > inclined > to default to EOL'ing everything that that isn't a deployment project. > > That is to say I'm suggesting that: > openstack/cloudkitty cloudkitty 1 > openstack/cloudkitty-dashboard cloudkitty 1 > openstack/cloudpulse BigTent > openstack/compute-hyperv BigTent > openstack/fuel-plugin-purestorage-cinder BigTent > openstack/group-based-policy BigTent 4 > openstack/group-based-policy-automation BigTent > openstack/group-based-policy-ui BigTent > openstack/murano-apps murano 3 > openstack/nova-solver-scheduler BigTent > openstack/openstack-resource-agents BigTent > openstack/oslo-incubator oslo > openstack/powervc-driver BigTent 1 > openstack/python-cloudkittyclient cloudkitty 1 > openstack/python-cloudpulseclient BigTent > openstack/python-group-based-policy-client BigTent > openstack/swiftonfile BigTent > openstack/training-labs Documentation > openstack/yaql BigTent 2 > > Get added to the EOL list. > > With the following hanging back for a while as they might need small tweaks > based on the kilo-eol tag. > > openstack/cookbook-openstack-bare-metal Chef OpenStack > openstack/cookbook-openstack-block-storage Chef OpenStack > openstack/cookbook-openstack-client Chef OpenStack > openstack/cookbook-openstack-common Chef OpenStack > openstack/cookbook-openstack-compute Chef OpenStack > openstack/cookbook-openstack-dashboard Chef OpenStack > openstack/cookbook-openstack-data-processing Chef OpenStack > openstack/cookbook-openstack-database Chef OpenStack > openstack/cookbook-openstack-identity Chef OpenStack > openstack/cookbook-openstack-image Chef OpenStack > openstack/cookbook-openstack-integration-test Chef OpenStack > openstack/cookbook-openstack-network Chef OpenStack > openstack/cookbook-openstack-object-storage Chef OpenStack > openstack/cookbook-openstack-ops-database Chef OpenStack > openstack/cookbook-openstack-ops-messaging Chef OpenStack > openstack/cookbook-openstack-orchestration Chef OpenStack > openstack/cookbook-openstack-telemetry Chef OpenStack > openstack/openstack-ansible OpenStackAnsible > openstack/openstack-chef-repo Chef OpenStack > openstack/packstack BigTent > > 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 > -- Serg Melikyan, Development Manager at Mirantis, Inc. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-re
Re: [openstack-dev] [stable][all] Tagging kilo-eol for "the world"
I’ve submitted a request to release all the unreleased code we still have for murano repositories https://review.openstack.org/#/c/325359/ ; It would be really great if we could get one final release before EOL’ing kilo in murano, murano-dashboard, murano-agent and python-muranoclient, if that is possible. After that I believe kilo branches in those repos are ready to be EOL’ed and deleted. -- Kirill Zaitsev Software Engineer Mirantis, Inc On 3 June 2016 at 09:26:58, Tony Breeds (t...@bakeyournoodle.com) wrote: On Thu, Jun 02, 2016 at 08:31:43PM +1000, Tony Breeds wrote: > Hi all, > In early May we tagged/EOL'd several (13) projects. We'd like to do a > final round for a more complete set. We looked for projects 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 is listed in governance:reference/projects.yaml and is tagged > with 'release:managed' or 'stable:follows-policy' (or both). So We've had a few people opt into EOL'ing which is great. I've Moved the lists from paste.o.o to a gist. The reason for that is I can update them, the URL doesn't change and there is a revision history (or sorts). The 2 lists are now at: https://gist.github.com/tbreeds/7de812a5d363fab4bd425beae5084c87 Given that there are now only 39 repos that are not (yet) EOL'ing I'm inclined to default to EOL'ing everything that that isn't a deployment project. That is to say I'm suggesting that: openstack/cloudkitty cloudkitty 1 openstack/cloudkitty-dashboard cloudkitty 1 openstack/cloudpulse BigTent openstack/compute-hyperv BigTent openstack/fuel-plugin-purestorage-cinder BigTent openstack/group-based-policy BigTent 4 openstack/group-based-policy-automation BigTent openstack/group-based-policy-ui BigTent openstack/murano-apps murano 3 openstack/nova-solver-scheduler BigTent openstack/openstack-resource-agents BigTent openstack/oslo-incubator oslo openstack/powervc-driver BigTent 1 openstack/python-cloudkittyclient cloudkitty 1 openstack/python-cloudpulseclient BigTent openstack/python-group-based-policy-client BigTent openstack/swiftonfile BigTent openstack/training-labs Documentation openstack/yaql BigTent 2 Get added to the EOL list. With the following hanging back for a while as they might need small tweaks based on the kilo-eol tag. openstack/cookbook-openstack-bare-metal Chef OpenStack openstack/cookbook-openstack-block-storage Chef OpenStack openstack/cookbook-openstack-client Chef OpenStack openstack/cookbook-openstack-common Chef OpenStack openstack/cookbook-openstack-compute Chef OpenStack openstack/cookbook-openstack-dashboard Chef OpenStack openstack/cookbook-openstack-data-processing Chef OpenStack openstack/cookbook-openstack-database Chef OpenStack openstack/cookbook-openstack-identity Chef OpenStack openstack/cookbook-openstack-image Chef OpenStack openstack/cookbook-openstack-integration-test Chef OpenStack openstack/cookbook-openstack-network Chef OpenStack openstack/cookbook-openstack-object-storage Chef OpenStack openstack/cookbook-openstack-ops-database Chef OpenStack openstack/cookbook-openstack-ops-messaging Chef OpenStack openstack/cookbook-openstack-orchestration Chef OpenStack openstack/cookbook-openstack-telemetry Chef OpenStack openstack/openstack-ansible OpenStackAnsible openstack/openstack-chef-repo Chef OpenStack openstack/packstack BigTent 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] [stable][all] Tagging kilo-eol for "the world"
On Fri, Jun 03, 2016 at 03:05:36PM +0200, Alan Pevec wrote: > > openstack/packstack BigTent > > Just to clarify, Packstack has not formally applied to BigTent yet, it > has only been automatically migrated from stackforge to openstack > namespace. Okay thanks. 'BitTent' is probably the wrong term there, for the purposes of this it just means not accosiatced with a project from governance:reference/projects.yaml > But yes, please keep its kilo branch for now until we properly wrap it up. Cool. 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] [stable][all] Tagging kilo-eol for "the world"
On Thu, Jun 2, 2016 at 7:32 PM, Tony Breeds wrote: > On Thu, Jun 02, 2016 at 07:10:23PM -0400, Emilien Macchi wrote: > >> I think that all openstack/puppet-* projects that have stable/kilo can >> be kilo-EOLed. >> Let me know if it's ok and I'll abandon all open reviews. > > Totally fine with me. > > I've added them. Feel free to abanond the reviews. Any you don't get to by > 2016-06-09 00:00 UTC I'll take care of. Done. https://review.openstack.org/#/q/branch:stable/kilo+project:%22%255Eopenstack/puppet-.*%2524%22+status:open,n,z 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 > -- 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] [stable][all] Tagging kilo-eol for "the world"
> openstack/packstack BigTent Just to clarify, Packstack has not formally applied to BigTent yet, it has only been automatically migrated from stackforge to openstack namespace. But yes, please keep its kilo branch for now until we properly wrap it up. Cheers, Alan __ 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] [stable][all] Tagging kilo-eol for "the world"
On Fri, Jun 03, 2016 at 09:29:34AM +0200, Matthias Runge wrote: > On 02/06/16 12:31, Tony Breeds wrote: > > The list of 171 projects that match above is at [1]. There are > > another 68 > I just abandoned open reviews for django_openstack_auth in kilo version. 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] [stable][all] Tagging kilo-eol for "the world"
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 02/06/16 12:31, Tony Breeds wrote: > Hi all, In early May we tagged/EOL'd several (13) projects. We'd > like to do a final round for a more complete set. We looked for > projects 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 is listed in governance:reference/projects.yaml and is > tagged with 'release:managed' or 'stable:follows-policy' (or > both). > > The list of 171 projects that match above is at [1]. There are > another 68 I just abandoned open reviews for django_openstack_auth in kilo version. django_openstack_auth is tightly coupled with horizon and should follow the same schedule. - -- Matthias Runge Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243, Managing Directors: Charles Cachera, Michael Cunningham, Michael O'Neill, Eric Shander -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJXUTHeAAoJEBdpskgc9eOLNEIQAJtrEvtmCyEWo1aozIZOJSyp +by9HO7s4UzP2wUmR5WpAG0w4wFDIlloY1i+jeRh9nDrSVJiyBqu7VKetgIhcEyP Zcg+ACVzLUzM5cCDuGR9892yO7jo+M9ez8i9UORiCHi4Q5rqok6EyykEWCDgue1X WMOJG+pTobdwA25bb9Eoq+3QNg/K988qzs0Y2JG+bU2chtcxLeJEfoeji1yEfnhE rvpNfLlXOhaR8eN9ZguoEX2eAXGFy9uMLbk5r9kAGG7IPoq41Lkry47qJkOEtR7e ztwqEfEy3BTTIi+bgV56HJRjZoirgj6+5pOmsXVN+CUJUVCrESK8yLIBORaj5LzN pFssS5b4h/j7/MShkV1AbltbrQNbiKJw/0CHjvxKll0bHpgfSedqGJCPfWZQvHqF qXODns0dmIS2xvFU8dBhLpAuRG5kirUzTXJb/Rfaknta7Smz5IWQ7lW37eeDvrrz /LDo3P4gQa8jaSj/1ye4QYnTulRgOw5TGitctHofzKPxfm+oPu3p2/QR08kAWA/g HUAenWrRkralksf5vX/vecW8lvZyyJBcKWeBVZbZQH5LHE062SwWHc0kXekgAmtT ewYUzWDBt0Afuwf70dl59GMlbk0wk4VT9awybBgMyRKmZI6UyAaVhLY0htcc2GZv wN+EdXCr4KNyPriWcT4T =U9ij -END 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] [stable][all] Tagging kilo-eol for "the world"
On Thu, Jun 02, 2016 at 08:31:43PM +1000, Tony Breeds wrote: > Hi all, > In early May we tagged/EOL'd several (13) projects. We'd like to do a > final round for a more complete set. We looked for projects 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 is listed in governance:reference/projects.yaml and is tagged > with 'release:managed' or 'stable:follows-policy' (or both). So We've had a few people opt into EOL'ing which is great. I've Moved the lists from paste.o.o to a gist. The reason for that is I can update them, the URL doesn't change and there is a revision history (or sorts). The 2 lists are now at: https://gist.github.com/tbreeds/7de812a5d363fab4bd425beae5084c87 Given that there are now only 39 repos that are not (yet) EOL'ing I'm inclined to default to EOL'ing everything that that isn't a deployment project. That is to say I'm suggesting that: openstack/cloudkitty cloudkitty 1 openstack/cloudkitty-dashboardcloudkitty 1 openstack/cloudpulse BigTent openstack/compute-hyperv BigTent openstack/fuel-plugin-purestorage-cinder BigTent openstack/group-based-policy BigTent 4 openstack/group-based-policy-automation BigTent openstack/group-based-policy-ui BigTent openstack/murano-apps murano 3 openstack/nova-solver-scheduler BigTent openstack/openstack-resource-agents BigTent openstack/oslo-incubatoroslo openstack/powervc-driver BigTent 1 openstack/python-cloudkittyclient cloudkitty 1 openstack/python-cloudpulseclientBigTent openstack/python-group-based-policy-client BigTent openstack/swiftonfileBigTent openstack/training-labsDocumentation openstack/yaql BigTent 2 Get added to the EOL list. With the following hanging back for a while as they might need small tweaks based on the kilo-eol tag. openstack/cookbook-openstack-bare-metal Chef OpenStack openstack/cookbook-openstack-block-storageChef OpenStack openstack/cookbook-openstack-client Chef OpenStack openstack/cookbook-openstack-common Chef OpenStack openstack/cookbook-openstack-compute Chef OpenStack openstack/cookbook-openstack-dashboardChef OpenStack openstack/cookbook-openstack-data-processing Chef OpenStack openstack/cookbook-openstack-database Chef OpenStack openstack/cookbook-openstack-identity Chef OpenStack openstack/cookbook-openstack-imageChef OpenStack openstack/cookbook-openstack-integration-test Chef OpenStack openstack/cookbook-openstack-network Chef OpenStack openstack/cookbook-openstack-object-storage Chef OpenStack openstack/cookbook-openstack-ops-database Chef OpenStack openstack/cookbook-openstack-ops-messagingChef OpenStack openstack/cookbook-openstack-orchestrationChef OpenStack openstack/cookbook-openstack-telemetryChef OpenStack openstack/openstack-ansible OpenStackAnsible openstack/openstack-chef-repo Chef OpenStack openstack/packstack BigTent 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] [stable][all] Tagging kilo-eol for "the world"
On Thu, Jun 02, 2016 at 08:41:40AM -0700, John Dickinson wrote: > open swift/swiftclient patches to stable/kilo have been abandoned Thanks John 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] [stable][all] Tagging kilo-eol for "the world"
On Thu, Jun 02, 2016 at 07:10:23PM -0400, Emilien Macchi wrote: > I think that all openstack/puppet-* projects that have stable/kilo can > be kilo-EOLed. > Let me know if it's ok and I'll abandon all open reviews. Totally fine with me. I've added them. Feel free to abanond the reviews. Any you don't get to by 2016-06-09 00:00 UTC I'll take care of. 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] [stable][all] Tagging kilo-eol for "the world"
On Thu, Jun 02, 2016 at 12:38:15PM +0200, Ihar Hrachyshka wrote: > I think all networking-* repos should EOL too, since they are plugins to > neutron which is already EOL. I struggle to find a way that could maintain > their gate without neutron. Thanks I've added them. 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] [stable][all] Tagging kilo-eol for "the world"
On Thu, Jun 2, 2016 at 6:31 AM, Tony Breeds wrote: > Hi all, > In early May we tagged/EOL'd several (13) projects. We'd like to do a > final round for a more complete set. We looked for projects 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 is listed in governance:reference/projects.yaml and is tagged > with 'release:managed' or 'stable:follows-policy' (or both). > > The list of 171 projects that match above is at [1]. There are another 68 > projects at [2] that have kilo branches but do NOT match the criteria above. > > Please look over both lists by 2016-06-09 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. > - A project is in list 2 that would like to opt *IN* to tagging/EOLing I think that all openstack/puppet-* projects that have stable/kilo can be kilo-EOLed. Let me know if it's ok and I'll abandon all open reviews. Thanks, > 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. > > I'd like to hand over the list of ready to EOL repos to the infra team on > 2016-09-10 (UTC) > > Yours Tony. > [1] http://paste.openstack.org/show/507233/ > [2] http://paste.openstack.org/show/507232/ > > __ > 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] [stable][all] Tagging kilo-eol for "the world"
open swift/swiftclient patches to stable/kilo have been abandoned --John On 2 Jun 2016, at 4:45, Jesse Pretorius wrote: > Hi Tony, > > OpenStack-Ansible is just waiting for the requirements repository and the > swift repository kilo-eol tags. Once they're done we'd like to bump the > SHA's for our 'kilo' to the EOL tags of those two repositories, tag a > release, then do our own kilo-eol tag. > > Thanks, > > Jesse > IRC: odyssey4me > > On 2 June 2016 at 11:31, Tony Breeds wrote: > >> Hi all, >> In early May we tagged/EOL'd several (13) projects. We'd like to do a >> final round for a more complete set. We looked for projects 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 is listed in governance:reference/projects.yaml and is tagged >> with 'release:managed' or 'stable:follows-policy' (or both). >> >> The list of 171 projects that match above is at [1]. There are another 68 >> projects at [2] that have kilo branches but do NOT match the criteria >> above. >> >> Please look over both lists by 2016-06-09 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. >> - 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. >> >> I'd like to hand over the list of ready to EOL repos to the infra team on >> 2016-09-10 (UTC) >> >> Yours Tony. >> [1] http://paste.openstack.org/show/507233/ >> [2] http://paste.openstack.org/show/507232/ >> >> __ >> 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 >> >> > > > -- > Jesse Pretorius > mobile: +44 7586 906045 > email: jesse.pretor...@gmail.com > skype: jesse.pretorius > __ > 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: OpenPGP digital 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] [stable][all] Tagging kilo-eol for "the world"
Hi Tony, OpenStack-Ansible is just waiting for the requirements repository and the swift repository kilo-eol tags. Once they're done we'd like to bump the SHA's for our 'kilo' to the EOL tags of those two repositories, tag a release, then do our own kilo-eol tag. Thanks, Jesse IRC: odyssey4me On 2 June 2016 at 11:31, Tony Breeds wrote: > Hi all, > In early May we tagged/EOL'd several (13) projects. We'd like to do a > final round for a more complete set. We looked for projects 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 is listed in governance:reference/projects.yaml and is tagged > with 'release:managed' or 'stable:follows-policy' (or both). > > The list of 171 projects that match above is at [1]. There are another 68 > projects at [2] that have kilo branches but do NOT match the criteria > above. > > Please look over both lists by 2016-06-09 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. > - 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. > > I'd like to hand over the list of ready to EOL repos to the infra team on > 2016-09-10 (UTC) > > Yours Tony. > [1] http://paste.openstack.org/show/507233/ > [2] http://paste.openstack.org/show/507232/ > > __ > 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 > > -- Jesse Pretorius mobile: +44 7586 906045 email: jesse.pretor...@gmail.com skype: jesse.pretorius __ 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] [stable][all] Tagging kilo-eol for "the world"
I think all networking-* repos should EOL too, since they are plugins to neutron which is already EOL. I struggle to find a way that could maintain their gate without neutron. > On 02 Jun 2016, at 12:31, Tony Breeds wrote: > > Hi all, >In early May we tagged/EOL'd several (13) projects. We'd like to do a > final round for a more complete set. We looked for projects 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 is listed in governance:reference/projects.yaml and is tagged > with 'release:managed' or 'stable:follows-policy' (or both). > > The list of 171 projects that match above is at [1]. There are another 68 > projects at [2] that have kilo branches but do NOT match the criteria above. > > Please look over both lists by 2016-06-09 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. > - 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. > > I'd like to hand over the list of ready to EOL repos to the infra team on > 2016-09-10 (UTC) > > Yours Tony. > [1] http://paste.openstack.org/show/507233/ > [2] http://paste.openstack.org/show/507232/ > __ > 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
[openstack-dev] [stable][all] Tagging kilo-eol for "the world"
Hi all, In early May we tagged/EOL'd several (13) projects. We'd like to do a final round for a more complete set. We looked for projects 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 is listed in governance:reference/projects.yaml and is tagged with 'release:managed' or 'stable:follows-policy' (or both). The list of 171 projects that match above is at [1]. There are another 68 projects at [2] that have kilo branches but do NOT match the criteria above. Please look over both lists by 2016-06-09 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. - 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. I'd like to hand over the list of ready to EOL repos to the infra team on 2016-09-10 (UTC) Yours Tony. [1] http://paste.openstack.org/show/507233/ [2] http://paste.openstack.org/show/507232/ 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
