[openstack-dev] [kolla][vote] deprecation of icehosue/juno/kilo branches

Sam Yaple samuel at yaple.net
Fri Mar 25 18:03:26 UTC 2016


+1

Sam Yaple

On Fri, Mar 25, 2016 at 4:52 PM, Michał Jastrzębski <inc007 at gmail.com>
wrote:

> +1
>
> On 25 March 2016 at 11:36, Jeffrey Zhang <zhang.lei.fly at gmail.com> wrote:
> > +1
> >
> > On Sat, Mar 26, 2016 at 12:07 AM, Ryan Hallisey <rhallise at redhat.com>
> wrote:
> >>
> >> +1 for sure
> >>
> >> -Ryan
> >>
> >> ----- Original Message -----
> >> From: "Paul Bourke" <paul.bourke at oracle.com>
> >> To: openstack-dev at lists.openstack.org
> >> Sent: Friday, March 25, 2016 11:43:06 AM
> >> Subject: Re: [openstack-dev] [kolla][vote] deprecation of
> >> icehosue/juno/kilo branches
> >>
> >> +1
> >>
> >> On 25/03/16 15:36, Steven Dake (stdake) wrote:
> >> > Hey folks,
> >> >
> >> > These branches are essentially unmaintained and we have completely
> given
> >> > up on them.  That’s ok – they were paths of our development.  I didn't
> >> > really want to branch them in the first place, but the community
> >> > demanded it, so I delivered that :)
> >> >
> >> > Now that our architecture is fairly stable in liberty and mitaka, I
> >> > think it makes sense to do the following
> >> > 1.. tag each of the above branches with icehosue-eol, juno-eol,
> kilo-eol
> >> > 2. Ask infrastructure to remove the branches from git
> >> >
> >> > This is possible; I have just verified in openstack-infra.  I'd like a
> >> > vote from the core review team.  If you would like to see the kilo
> >> > branch stay, please note that, and if there is a majority on
> >> > icehosue/juno but not kilo I'll make the appropriate arrangements with
> >> > openstack-infra.
> >> >
> >> > I will leave voting open for 1 week until Saturday April 2nd.  I will
> >> > close voting early if there is a majority vote.
> >> >
> >> > Regards
> >> > -steve
> >> >
> >> >
> >> >
> >> >
> __________________________________________________________________________
> >> > 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
> >> >
> >>
> >>
> __________________________________________________________________________
> >> 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
> >>
> >>
> __________________________________________________________________________
> >> 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
> >
> >
> >
> >
> > --
> > Jeffrey Zhang
> > Blog: http://xcodest.me
> >
> >
> __________________________________________________________________________
> > 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
> >
>
> __________________________________________________________________________
> 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/20160325/41563e55/attachment.html>


More information about the OpenStack-dev mailing list