Re: [cordova-cli] npm Version Update

2013-04-21 Thread Brian LeRoux
> The first step will be to lazy load the locked in version. Ok. So we are version locked. But MINOR has different meaning from a native project to the CLI tools. > The much longer goal would be to discuss and architect the grunt inspired > approach. However, with how the CLI is structured, it w

Re: [cordova-cli] npm Version Update

2013-04-20 Thread Michael Brooks
The first step will be to lazy load the locked in version. This ensures that the npm install isn't huge and downloading platforms that the developer is not interested it. It also allows us to lazy load patched releases almost instantaneously - no npm update required. The much longer goal would be

Re: [cordova-cli] npm Version Update

2013-04-20 Thread Brian LeRoux
So wait, I had thought thats what you were doing w/ the CLI right now? Or is lazy loading just lazy loading version lock then? On Fri, Apr 19, 2013 at 3:06 PM, Michael Brooks wrote: > Totally down with this Brian. However, it doesn't exist today and > realistically it wouldn't exist before 3.0.0.

Re: [cordova-cli] npm Version Update

2013-04-19 Thread Michael Brooks
Totally down with this Brian. However, it doesn't exist today and realistically it wouldn't exist before 3.0.0. My proposed versioning allows us have both today and allows us to transition to an independent CLI version in the future. Today, we can reliably track both the Cordova framework version

Re: [cordova-cli] npm Version Update

2013-04-19 Thread Brian LeRoux
Cordova CLI has a version that is independent of the Cordova releases. (Once we decouple the creating of projects from version locking.) So I create a project today with Cordova CLI it would use the most recent release. Lets pretend that's 2.7. Cool. A month later I create a project with the CLI a

Re: [cordova-cli] npm Version Update

2013-04-19 Thread Michael Brooks
> > Why not independently version? Can you elaborate? I don't understand how that work under both the Cordova project and as a consumable npm module. On Fri, Apr 19, 2013 at 3:28 PM, Brian LeRoux wrote: > I don't get it. Why not independently version? > > (I recognize we version lock currentl

Re: [cordova-cli] npm Version Update

2013-04-19 Thread Brian LeRoux
I don't get it. Why not independently version? (I recognize we version lock currently.) On Fri, Apr 19, 2013 at 2:19 PM, Filip Maj wrote: > Rockin, love it > > On 4/19/13 2:17 PM, "Michael Brooks" wrote: > >>Hey all, >> >>I'm planning to change the way we version the Cordova CLI. >> >>TL;DR >>

Re: [cordova-cli] npm Version Update

2013-04-19 Thread Filip Maj
Rockin, love it On 4/19/13 2:17 PM, "Michael Brooks" wrote: >Hey all, > >I'm planning to change the way we version the Cordova CLI. > >TL;DR >--- > > 2.7.0+1.0.5 === Cordova 2.7.0 and npm module version 1.0.5 > 2.7.1+1.0.12 === Cordova 2.7.1 and npm module version 1.0.12 > >Current State >---

[cordova-cli] npm Version Update

2013-04-19 Thread Michael Brooks
Hey all, I'm planning to change the way we version the Cordova CLI. TL;DR --- 2.7.0+1.0.5 === Cordova 2.7.0 and npm module version 1.0.5 2.7.1+1.0.12 === Cordova 2.7.1 and npm module version 1.0.12 Current State --- Today, the Cordova CLI uses a major.minor.patch version identifiers to pu