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

Samuel Cassiba sam at cassiba.com
Wed Jan 6 16:22:25 UTC 2016

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 branches are actually supported.

On Wed, Jan 6, 2016 at 5:50 AM, Jan Klare <j.klare at cloudbau.de> wrote:

> 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 define which branches exactly we want to keep. As far
> as i remember we agreed on supporting n + 1, which would be stable/kilo and
> stable/liberty imho. I would like to remove all the unsupported branches as
> fast as possible to clean this up. If you think otherwise, please write an
> short answer to this mailing list until the end of this week. If nothing
> prevents the cleanup, i will contact infra at the beginning of the next
> week and ask them to help me with the deletion of all old and unsupported
> branches.
> Cheers,
> Jan
> —————————
> irc: jklare
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160106/bc70535b/attachment.html>

More information about the OpenStack-dev mailing list