st
> > > > >> > step.
> > > > >> > >>
> > > > >> > >> *Jeff Hair*
> > > > >> > >> Technical Lead and Software Developer
> > >
, Mar 15, 2017 at 8:18 AM, Rohit Yadav <
> > > >> > rohit.ya...@shapeblue.com>
> > > >> > >> wrote:
> > > >> > >>
> > > >> > >> > +1 as others have noted
Looks good to me.
;
> > > >> > >> Tel: (+354) 415 0200
> > > >> > >> j...@greenqloud.com
> > > >> > >> www.greenqloud.com
> > > >> > >>
> > > >> > >> O
>>
> > >> > >> On Wed, Mar 15, 2017 at 8:18 AM, Rohit Yadav <
> > >> > rohit.ya...@shapeblue.com>
> > >> > >> wrote:
> > >> > >>
> > >> > >> > +1 as others have noted
> &g
>> Tel: (+354) 415 0200
> > >> > >> j...@greenqloud.com
> > >> > >> www.greenqloud.com
> > >> > >>
> > >> > >> On Wed, Mar 15, 2017 at 8:18 AM, Rohit Yadav <
> > >> > rohit.ya...@shapeblue.com>
> > >> > >> wrote:
> >
>> >
> >> > >> > Disable the plugin from the default build for next few
> releases
> >> > and
> >> > >> > eventually deprecate/remove the plugin from the codebase. The
> >> > roadmap can
> >> > >> >
few releases
>> > and
>> > >> > eventually deprecate/remove the plugin from the codebase. The
>> > roadmap can
>> > >> > look something like:
>> > >> >
>> > >> > - Announce on the MLs that we're planning to do t
nnounce on the MLs that we're planning to do this, send a PR
> > and get
> > >> it
> > >> > accepted
> > >> >
> > >> > - During the release process RM should make this information
> > available to
> > >> > everyone
> >> > everyone (including voting thread, would be nice to have a
> > shortlog of
> > >> > major changes in the voting email?)
> > >> >
> > >> > - In the release notes and releas
ice to have a
> shortlog of
> >> > major changes in the voting email?)
> >> >
> >> > - In the release notes and release announcement, note that
> midonet is no
> >> > longer included in the default build and is planned to be
> deprecated
> &g
ncement
>> >
>> >
>> > I think this should be done with Midonet and any other plugins that are
>> > causing issues and are no longer maintained by anyway.
>> >
>> >
>> > Regards.
>&
, if we've no communication received deprecate and
>> > remove the plugin with an announcement
>> >
>> >
>> > I think this should be done with Midonet and any other plugins that are
>> > causing issues and are no longer maintained by anyway.
>&g
Giving the community at large some
> time to yell if they are using is good.
>
> Regards,
> Marty Godsey
> Principal Engineer
> nSource Solutions, LLC
>
> -Original Message-
> From: Will Stevens [mailto:williamstev...@gmail.com]
> Sen
sey
Principal Engineer
nSource Solutions, LLC
-Original Message-
From: Will Stevens [mailto:williamstev...@gmail.com]
Sent: Sunday, March 19, 2017 7:39 AM
To: dev@cloudstack.apache.org
Subject: Re: [DISCUSS] Retirement of midonet plugin
I think there nee
ll Stevens [mailto:williamstev...@gmail.com]
Sent: Sunday, March 19, 2017 7:39 AM
To: dev@cloudstack.apache.org
Subject: Re: [DISCUSS] Retirement of midonet plugin
I think there needs to be at least 6 months between the disable code being
released and the delete PR being merged. I feel like the
gt; > > remove the plugin with an announcement
> > >
> > >
> > > I think this should be done with Midonet and any other plugins
> that are
> > > causing issues and are no longer maintained by anyway
available to
>> > > everyone (including voting thread, would be nice to have a
>> shortlog of
>> > > major changes in the voting email?)
>> > >
>> > > - In the release notes and release announcement, note that
>> midonet is no
>
Midonet and any other plugins that are
> > causing issues and are no longer maintained by anyway.
> >
> >
> > Regards.
> >
> >
> > From: Sergey Levitskiy <sergey.levits...@autodesk.com>
eived deprecate and
> > remove the plugin with an announcement
> >
> >
> > I think this should be done with Midonet and any other plugins that are
> > causing issues and are no longer maintained by anyway.
> >
> >
> > Regards.
> >
> > __
an announcement
>
>
> I think this should be done with Midonet and any other plugins that are
> causing issues and are no longer maintained by anyway.
>
>
> Regards.
>
>
> From: Sergey Levitskiy <sergey.levits...@autodesk.com>
: Sergey Levitskiy <sergey.levits...@autodesk.com>
Sent: 15 March 2017 07:00:51
To: dev@cloudstack.apache.org
Subject: Re: [DISCUSS] Retirement of midonet plugin
I am for:
(i) disable the build for the plugin for the next 2 major release followed by
(ii) remove everything in ACS 4.12 if
Received: Tuesday, 14 Mar 2017, 9:10PM
To: dev@cloudstack.apache.org [dev@cloudstack.apache.org]
Subject: [DISCUSS] Retirement of midonet plugin
Dear ACS fellows,
Recently there have been two threads asking and discussing the “midonet”
integra
art...@gmail.com]
Received: Tuesday, 14 Mar 2017, 9:10PM
To: dev@cloudstack.apache.org [dev@cloudstack.apache.org]
Subject: [DISCUSS] Retirement of midonet plugin
Dear ACS fellows,
Recently there have been two threads asking and discussing the “midonet”
integration with Apache
I agree with Sergey and Will. Let's disable it first.
Simon Weller/615-312-6068
-Original Message-
From: Rafael Weingärtner [rafaelweingart...@gmail.com]
Received: Tuesday, 14 Mar 2017, 9:10PM
To: dev@cloudstack.apache.org [dev@cloudstack.apache.org]
Subject: [DISCUSS] Retirement
I think we approach these with a disable, then delete approach. Disable for
one or two releases and if no one steps in to revive it in that period, we
delete it.
On Mar 14, 2017 9:10 PM, "Rafael Weingärtner"
wrote:
Dear ACS fellows,
Recently there have been two
I am for:
(i) disable the build for the plugin for the next 2 major release followed by
(ii) remove everything in ACS 4.12 if no one express regrets by then
Dear ACS fellows,
Recently there have been two threads asking and discussing the “midonet”
integration with Apache CloudStack (ACS) [1-2].
After quite some discussions, we noticed that despite having some people
willing to use it, the plugin has never been fully developed by its vendor
28 matches
Mail list logo