> cordova-windows won't as it has the dependency listed as ^1.0.0 which 
> includes minor releases.
IMO since cordova-common is a bundled dependency, we still need for new release 
to bundle new version.

A small question - do we need for blog post for this release? I'd say no, as we 
releasing something for internal use, but what is your thoughts?

-
Best regards, Vladimir

-----Original Message-----
From: Steven Gill [mailto:[email protected]] 
Sent: Tuesday, February 16, 2016 7:49 AM
To: [email protected]
Subject: Re: [DISCUSS] Cordova-common 1.1.0 release

Yes. I'd like us to go ^1.0.0 and include minors. Just need to be careful when 
doing minor common releases to not break platforms.
On Feb 15, 2016 8:11 PM, "Carlos Santana" <[email protected]> wrote:

> Should we be consistent about how we declare the dependency for 
> platforms against cordova-common ?
>
>
>
> On Mon, Feb 15, 2016 at 11:04 PM Steven Gill <[email protected]>
> wrote:
>
> > Sounds good.
> >
> > Cordova-lib, Cordova-android and cordova-ios will need to have 
> > releases with this updated cordova-common.
> >
> > cordova-windows won't as it has the dependency listed as ^1.0.0 
> > which includes minor releases.
> >
> > On Mon, Feb 15, 2016 at 6:29 AM, Vladimir Kotikov (Akvelon) < 
> > [email protected]> wrote:
> >
> > > Hi, guys.
> > > I'm planning to do a minor release for cordova-common.
> > >
> > > Here is the list of JIRAs to be resolved in this release (aka
> > > RELEASENOTES):
> > >
> > > * CB-10052 Improve superspawn to allow to handle spawned process 
> > > io
> > streams
> > > * CB-10176 Cordova-common should contain a default logger
> implementation
> > > * CB-10430 cordova-common events don't reach platform's code
> > > * CB-10497 android build with ant fails
> > >
> > > The version to be released is [email protected]
> > >
> > > Does anyone have any reason to delay a tools release?
> > > Any outstanding patches to land?
> > >
> > > If not, I will start the release on Wed, 16th.
> > >
> > > -
> > > Best regards, Vladimir
> > >
> > > ------------------------------------------------------------------
> > > --- 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