Re: [openstack-dev] [chef] deprecation and removal of old branches

Hi, i talked to infra and they can remove all of our old branches, but would also like us to tag them first. To do this, i (as the PTL) need to push these signed tags directly to gerrit. To be able to do this i need to adapt our gerrit acls and allow this. While i walked through the whole proce

Re: [openstack-dev] [chef] deprecation and removal of old branches

Hi, Good point, i will talk to infra and figure out how to properly push these eol tags to the last commits of the branches before we remove them. Since i only got positive feedback on this, i will also go ahead and ask them to help me with the cleanup. Cheers, Jan > On 07 Jan 2016, at 07:42

Re: [openstack-dev] [chef] deprecation and removal of old branches

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 1/6/16 10:22 AM, Samuel Cassiba wrote: > I'm +1 on this idea. Looking at other OpenStack projects (Nova, Neutron, > etc.) on GitHub, they only have stable/liberty and stable/kilo Sounds good to me too. - -- Best Regards, JJ Asghar c: 512.619.0

Re: [openstack-dev] [chef] deprecation and removal of old branches

I'm +1 on this idea. Looking at other OpenStack projects (Nova, Neutron, etc.) on GitHub, they only have stable/liberty and stable/kilo, with anything older dropped. We're already following this support model, so I think the cleanup should happen, that way there isn't any ambiguity on which branche

[openstack-dev] [chef] deprecation and removal of old branches

Hi everybody, due to a hint on this patch https://review.openstack.org/#/c/264130/1 i walked through some of our cookbooks and found that we never actually deprecated or removed the old branches for most of our cookbooks. To do this, we just need to d