Done! For 4.3.1,  we don't actually want to publish it as latest. So
publishing it as RC is actually good enough because it won't take over the
latest tag.
On Jun 1, 2015 6:10 PM, "Tim Barham" <[email protected]> wrote:

> BTW, I have done this as a partial release - I've updated lib and cli
> only. I just wanted to verify that's ok before I start the vote thread.
>
> There didn't seem any reason to update cordova-js, and the change
> shouldn't impact plugman (also plugman 0.23.0 is associated with 4.3.0 and
> 0.23.1 is associated with 5.0.0, so I'm not sure what version of plugman
> I'd make it :) ).
>
> Thanks,
>
> Tim
>
> -----Original Message-----
> From: Steven Gill [mailto:[email protected]]
> Sent: Monday, June 1, 2015 12:00 PM
> To: [email protected]
> Subject: RE: [DISCUSS] Cordova Tools release 4.3.1
>
> Sounds good.
>
> P. S. Obviously I meant cordova platform add not plugin add
> On Jun 1, 2015 11:55 AM, "Tim Barham" <[email protected]> wrote:
>
> > Thanks Steve... The use case here is for people not using the CLI
> > directly, but working with tools like Visual Studio. If they want to be
> on
> > 4.x for whatever reason, we'll use 4.3.1 so they get this security update
> > (and I was planning to modify the pinned platforms to use "~" versions
> like
> > we have done with 5.1.0 in case there are any other platform patches
> going
> > forwards).
> >
> > -----Original Message-----
> > From: Steven Gill [mailto:[email protected]]
> > Sent: Monday, June 1, 2015 11:13 AM
> > To: [email protected]
> > Subject: Re: [DISCUSS] Cordova Tools release 4.3.1
> >
> > It just feels like overkill to me. People on the 4series can easily
> cordova
> > plugin add [email protected].
> >
> > I won't block you though if you decide to proceed.
> > On Jun 1, 2015 10:06 AM, "Tim Barham" <[email protected]> wrote:
> >
> > > I'd like to propose a 4.3.1 Cordova Tools release to pin
> cordova-android
> > > 3.7.2 (security release - see
> > > http://cordova.apache.org/announcements/2015/05/26/android-402.html).
> > >
> > > Is anyone aware of any reasons not to proceed with this? If not, I'll
> > > proceed with it later today.
> > >
> > > Thanks!
> > >
> > > Tim
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected]
> > For additional commands, e-mail: [email protected]
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to