You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by Mark Koudritsky <ka...@google.com> on 2014/07/22 23:31:48 UTC

Proposal: remove platform versions from platfroms.js

Currently a release of our cli tools always downloads the same version of
platform files which is hard-coded incordova/platforms.js
<https://github.com/apache/cordova-lib/blob/master/cordova-lib/src/cordova/platforms.js>.
This makes it impossible to release new versions of platforms that would be
usable with the same version of CLI.

As the next step in decoupling platform releases I would like to remove the
hard-coded version in platform.js and let the CLI to download the latest
platform version available on npm by default.

Projects that need to use an older version can use either
cordova platform add <platform>@<version>
or for even more control
cordova platform add /path/to/local/checkout

Known issues:
 - platforms before 3.5.0 are not (yet) published on npm.
 - It will hit the network for every "platform add" that has no version
explicitly specified. In most cases the reply from npm will be an "HTTP 304
- Not Modified".
 - We'll have to add in some sort of check that the version of CLI that you
have works with the platform. E.g. current tools might not work with
cordova-5.0. In than case we can display an error that instructs the user
to either upgrade CLI or specify the platform version explicitly.

What do you think?

Re: Proposal: remove platform versions from platfroms.js

Posted by "Terence M. Bandoian" <te...@tmbsw.com>.
If I understand the terminology:

- CLI refers to a collection of utilities to download and install 
OS-specific application frameworks and plugins and build applications 
using those frameworks and plugins
- platforms refers to OS-specific software frameworks

If that's true, I would think that a very loose coupling between the two 
would make sense.

Including default versions for platforms and plugins in the CLI seems 
reasonable.  Allowing versions to be specified for platforms and plugins 
in CLI commands seems essential for development flexibility.

-Terence Bandoian


On 7/24/2014 1:17 PM, David Kemp wrote:
> It seems to me that:
> 1) to make our users happy and get them to consider using newer versions,
> we need to have the perception of stability. Nice clean, well tested,
> co-ordinated releases are a good way to get that. For that reason, I think
> a method of providing a 'pinned' release set for the end user is a good way
> to deliver that.
> 2) to make it easy and fast for the various platform contributors to
> release new stuff, we need independent platform versioning. That would
> allow platforms to move ahead separately - as long as all tooling is
> backward compatible.
>
> We should be able to do both.
>
>
>
> On Thu, Jul 24, 2014 at 1:38 PM, Brian LeRoux <b...@brian.io> wrote:
>
>> I am against this change. I am in favor of adding platforms via
>> package.json, however.
>>
>> We need to version lock our dependencies in the CLI. Testing and bug
>> resolution will be impossible otherwise. (We did this for that reason.)
>> However, the Platforms don't need to be synchronized. Platforms can release
>> as they want and the CLI can pick them up as needs be BUT the versioning of
>> dependencies needs to be explicit.
>>
>> The only way 'always grab latest' works is when master is pristine and all
>> development happens on topic branches only to be merged in when everything
>> works. That is not a capability we currently have.
>>
>> "This makes it impossible to release new versions of platforms that would
>> be
>> usable with the same version of CLI." <--- this is a feature, not a bug!
>> When we want to bump the platforms we *should* have to bump the CLI as it
>> is a dependency.
>>
>>
>>
>> On Thu, Jul 24, 2014 at 9:19 AM, Andrew Grieve <ag...@chromium.org>
>> wrote:
>>
>>> On Thu, Jul 24, 2014 at 10:40 AM, Chuck Lantz <cl...@microsoft.com>
>>> wrote:
>>>
>>>> To me it sounds like we're talking about something bigger than pinning:
>>>> What does a Cordova version actually mean?
>>>>
>>>> When new macro-level "Cordova" features like splash screens and icons
>>>> support or perhaps coming up with a way to manage code signing and
>>>> packaging without going into native projects are released, we'll need
>> to
>>> be
>>>> able to coordinate a release across a number of different platforms.
>>   So,
>>>> the way I've always thought about this from and end user perspective
>> is:
>>>
>>> Certainly having platforms at different versions will be a change from
>> what
>>> we've had historically. Still, I think it will be for the better.
>>>
>>>
>>>> -Updating the first digit is done for major Cordova level features that
>>>> affect everyone - and force everyone to change
>>>>
>>> But what if only one platform has a change that requires action? Do we
>> not
>>> bump the major then?, Or do we bump the major and users of other
>> platforms
>>> discover it doesn't actually affect them.
>>>
>>>
>>>> -Updating the second digit is about incremental improvements that still
>>>> constitute new Cordova level features but may only support certain
>>> platforms
>>>
>>> -Updating the last digit ties to bug fixes, perf improvements, and other
>>>> things that do not have a direct effect on end users
>>>
>>>> Two questions:
>>>> -How will documentation work if platforms go to versions independent of
>>>> one another?  For example, consider this:
>>>>
>>>>          Android goes to Cordova 3.7.0 one week
>>>>          iOS goes to Cordova 3.7.0 two weeks later
>>>
>>>> Does the documentation for the same version update?
>>>>
>>> I think the easiest way is to just not version the docs. Just have them
>>> always be up-to-date for all released platforms.
>>>
>>>
>>>
>>>> -Are we saying that there will never be shared infrastructure across
>>>> platforms that the CLI needs?  Otherwise you could get in a situation
>>> where
>>>> the CLI revs and only one or two platforms are actually supported.
>>   Given
>>>> Cordova really is about cross-platform/multi-device development, is
>> that
>>> a
>>>> message we want to send to end users?  What about plugins?
>>>>
>>> The latest version of CLI must always support all plugins (even old
>> ones),
>>> and all platform versions (even old ones). This (I believe), is already
>> the
>>> case today, and is not too hard to maintain.
>>>
>>>
>>>
>>>> I also think this commits the community to testing the CLI across a
>>> number
>>>> of different versions over time. The CLI would need to be validated
>>> across
>>>> a number of different major and minor versions which increases the test
>>>> burden.
>>>>
>>> I believe this to already be the case. The current workflow is:
>>>
>>> 1. Install a platform (say, android 3.2)
>>> 2. Update CLI to 3.5.0
>>> 3. CLI now expected to work with version of platform you have installed.
>>> 4. Decide you want to update your platform via "cordova platform update
>>> android"
>>> 5. Now, your project is at android 3.5.0
>>>
>>>
>>>
>>>> I would argue that plugins are a potential problem right now - the
>> moment
>>>> a core plugin drops support for a Cordova version that people are using
>>>> widely, I think we'll hear about it.  However, in the case of a plugin,
>>> it
>>>> is inherently multi-platform and its documentation and functionality
>>> across
>>>> all platforms will update with one version change.  I think that is the
>>>> issue with platforms - There needs to be a mechanism to communicate
>> that
>>>> something has changed across multiple platforms.
>>>>
>>> I think your plugin example is a great motivation for having things
>>> versioned separately. If a plugin drops support for android-3.0.0, then
>>> users are free to stick with an older version of the plugin that does
>>> support it. I do conceded that our tooling is currently not great about
>>> making this easy to do though.
>>>
>>> Plugin features almost always get added one platform at a time. Likewise
>>> with platform features. I don't think we should be striving to add
>> features
>>> across all platforms at a time, because not all platforms even have
>> people
>>> actively working on them. What's the gain in trying to synchronize them?
>> It
>>> would only cause things to be released more slowly.
>>>
>>> For example, we recently had icons and splashscreen support added to CLI
>>> for some but not all platforms. This actually required no changes in
>>> platforms, because platforms already supported both. This is a great
>>> example of why we'd want CLI to not be pinned to platform versions.
>> Someone
>>> running cordova-android@3.1.0 would get icon support if they updated
>> their
>>> version of CLI, and they wouldn't need to update their platform.
>>>
>>>
>>>
>>>> On the Android 4.0 churn vs fixes - this sounds more like a branching
>>>> problem that we should not pass on to end users.
>>>>
>>>> -Chuck
>>>>
>>>> -----Original Message-----
>>>> From: agrieve@google.com [mailto:agrieve@google.com] On Behalf Of
>> Andrew
>>>> Grieve
>>>> Sent: Thursday, July 24, 2014 6:47 AM
>>>> To: dev
>>>> Subject: Re: Proposal: remove platform versions from platfroms.js
>>>>
>>>> I agree that the feature will make installing platforms less
>>> predictable...
>>>> or at least, just as unpredictable as plugins.
>>>>
>>>> It is a good idea to look at exactly what the benefits are though.
>>>>
>>>> First - the benefits of removing the idea of a "cadence version":
>>>> - Android 4.0 is on the horizon, maybe iOS 4.0 as well. Does this mean
>>>> that when they are ready, we should force all platforms to jump to 4.0?
>>>> Wouldn't be too bad...
>>>> - But once at 4.0, what if Windows or Blackberry requires a major
>> release
>>>> a couple months later, move all platforms to 5.0?
>>>> - What if Android undergoes a lot of churn come 4.0, and wants to do 3
>>>> more bugfix releases within the first month after? Do we force all
>>>> platform's versions to be updated? If not, what does the cadence number
>>> on
>>>> CLI look like?
>>>> - Cadence versioning forces us to try and release multiple platforms at
>>>> the same time.
>>>>    - E.g. Jesse wants to release windows, but has been waiting for
>> Android
>>>> to be ready.
>>>>    - If each platform just released when it was ready, and had separate
>>>> blog posts, I think we'd have a happier release process, and would
>>> release
>>>> more often.
>>>>
>>>> Now, we could do away with cadence version and still have CLI use the
>>>> version in its platforms.js file for each platform. So what does this
>>>> specific change of removing the pinning buy us?
>>>> - It will lighten the load of doing platform releases.
>>>> - It will make platforms and plugins both work in the same way.
>>>>
>>>>
>>>>
>>>>
>>>> On Wed, Jul 23, 2014 at 2:49 PM, Jesse <pu...@gmail.com>
>> wrote:
>>>>> I agree, there are many cases where this will lead to complete
>>>>> un-predictability, and it is still unclear who this 'feature'
>> benefits.
>>>>> How can we guarantee that latest version of a newly added platform
>>>>> supports all the same plugins of the previously added platforms?
>>>>>
>>>>> I think ultimately the only benefit is to give us some flexibility
>>>>> with release schedules, but I would much rather have us focus on just
>>>>> releasing everything more often.  Historically we have never been
>> able
>>>>> to deliver a patched point release in under a month, so assuming we
>>>>> can get back to releasing every month, all would be fine, and the
>>>>> train could just keep rolling forwards. Predictably!
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> @purplecabbage
>>>>> risingj.com
>>>>>
>>>>>
>>>>> On Wed, Jul 23, 2014 at 10:59 AM, Parashuram Narasimhan (MS OPEN
>> TECH)
>>>>> < panarasi@microsoft.com> wrote:
>>>>>
>>>>>> I was thinking platforms are devDependencies and plugins are
>>>>>> dependencies
>>>>>> :)
>>>>>>
>>>>>> In a way, that’s how the bundling works - plugins are packaged with
>>>>>> the app, while platforms are only needed during development !!
>>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Anis KADRI [mailto:anis.kadri@gmail.com]
>>>>>> Sent: Wednesday, July 23, 2014 10:54 AM
>>>>>> To: dev@cordova.apache.org
>>>>>> Subject: Re: Proposal: remove platform versions from platfroms.js
>>>>>>
>>>>>> +1 for package.json for platforms. plugins might a bit trickier but
>>>>>> +still
>>>>>> doable, we could get rid of plugins/ but we somehow need to keep
>>>>>> track of them in node_modules/ (maybe use one of the 10 config
>> files
>>>> we have).
>>>>>> Platforms in package.json should cause no problems though,
>>>>>> add/remove platforms, pin/unpin versions if required.
>>>>>>
>>>>>>
>>>>>> On Wed, Jul 23, 2014 at 7:36 AM, Michal Mocny <mmocny@chromium.org
>>>>> wrote:
>>>>>>> This sounds like a great topic for hangout Friday.  Glad to have
>> a
>>>>>>> concrete proposal / some counter arguments to discuss.
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Jul 23, 2014 at 10:22 AM, Mark Koudritsky
>>>>>>> <ka...@google.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>>> Currently WebWorks ships specific versions of things.
>>>>>>>>> If we had shipped unpinned versions of stuff, then eventually
>>>>>>>>> we would have created projects which our UI wouldn't have
>>>>>>>>> recognized as valid (because, they e.g. Didn't have a
>>>>>>>>> ".cordova", or a "hooks", or a
>>>>>>> "merges"
>>>>>>>>> or whichever things we had been using to determine if a
>>>>>>>>> project was
>>>>>>>> valid).
>>>>>>>> As long as you continue to ship a version of cordova-backberry
>>>>>>>> bundled
>>>>>>> with
>>>>>>>> WebWorks, it won't be affected by the change I propose. CLI
>> will
>>>>>>>> use that bundled version just like it does now using the
>>>>>>>> settings in .cordova/config.json. We do the same thing with
>> cca.
>>>>>>>> If in the future you decide to stop bundling cordova-blackberry
>>>>>>>> with WebWorks and switch to the npm published versions, I see
>>>>>>>> several good
>>>>>>> ways
>>>>>>>> for doing that, but in any case, you will probably want to
>>>>>>>> expose the version (or range of versions) to use as a user
>>>> editable setting.


Re: Proposal: remove platform versions from platfroms.js

Posted by Andrew Grieve <ag...@chromium.org>.
On Thu, Jul 24, 2014 at 3:49 PM, Brian LeRoux <b...@brian.io> wrote:

> - ya I don't care at all about whatever we want the versioning scheme to be
>
> I don't see much benefit from this:
>
> "cordova platform add android@NEXT_VERSION"
>
> I'd rather see ppl update their tool to the next version of the CLI.
>

My thinking there was that we'll be able to announce platform updates
without waiting for a tools release to happen.


>
>
>
>
> On Thu, Jul 24, 2014 at 12:36 PM, Andrew Grieve <ag...@chromium.org>
> wrote:
>
> > How about discussing dropping the CAD-SEM version of CLI, and just have
> > SEM?
> >
> > Probably it'd still be good to go over what *exactly* the platform
> release
> > process should look like. E.g.:
> > - Any platform can be released at any time
> > - If it requires an update to cordova.js, then create a new cordova.js
> > version.
> > - Create a blog post just for your platform
> > - Tell users to try it out via "cordova platform add android@NEXT_VERSION
> "
> > - Next time tools release happens, CLI will have its default platform
> > version updated to include the new platform release.
> >
> >
> > On Thu, Jul 24, 2014 at 3:18 PM, Michal Mocny <mm...@chromium.org>
> wrote:
> >
> > > OOOOhhh, Brain you meant cordova-cli's package.json, not the project
> > > workspaces!  I like that.  I like that you can create a project while
> > > offline that way.  I'm also with David/Brian/Others that CLI can have a
> > > default pinned version set, yet we still get cordova platform version
> > > independance.
> > >
> > > I thought we were proposing creating a package.json as part of "cordova
> > > create" alongside config.xml, which I was really O_o about.  (I think
> > this
> > > is a likely direction we may end up, but not just nilly willy).
> > >
> > > Glad we are coming to agreement, but now we wont have anything to
> discuss
> > > Friday ;)
> > >
> > > -Michal
> > >
> > >
> > > On Thu, Jul 24, 2014 at 2:56 PM, Brian LeRoux <b...@brian.io> wrote:
> > >
> > > > totally agree. the cli package.json can capture which versions of the
> > > > platforms it needs. the platforms can release with reckless abandon
> > > >
> > > > (maybe we'll even hit THREE times this year! ;)
> > > >
> > > >
> > > > On Thu, Jul 24, 2014 at 11:17 AM, David Kemp <dr...@chromium.org>
> > > wrote:
> > > >
> > > > > It seems to me that:
> > > > > 1) to make our users happy and get them to consider using newer
> > > versions,
> > > > > we need to have the perception of stability. Nice clean, well
> tested,
> > > > > co-ordinated releases are a good way to get that. For that reason,
> I
> > > > think
> > > > > a method of providing a 'pinned' release set for the end user is a
> > good
> > > > way
> > > > > to deliver that.
> > > > > 2) to make it easy and fast for the various platform contributors
> to
> > > > > release new stuff, we need independent platform versioning. That
> > would
> > > > > allow platforms to move ahead separately - as long as all tooling
> is
> > > > > backward compatible.
> > > > >
> > > > > We should be able to do both.
> > > > >
> > > > >
> > > > >
> > > > > On Thu, Jul 24, 2014 at 1:38 PM, Brian LeRoux <b...@brian.io> wrote:
> > > > >
> > > > > > I am against this change. I am in favor of adding platforms via
> > > > > > package.json, however.
> > > > > >
> > > > > > We need to version lock our dependencies in the CLI. Testing and
> > bug
> > > > > > resolution will be impossible otherwise. (We did this for that
> > > reason.)
> > > > > > However, the Platforms don't need to be synchronized. Platforms
> can
> > > > > release
> > > > > > as they want and the CLI can pick them up as needs be BUT the
> > > > versioning
> > > > > of
> > > > > > dependencies needs to be explicit.
> > > > > >
> > > > > > The only way 'always grab latest' works is when master is
> pristine
> > > and
> > > > > all
> > > > > > development happens on topic branches only to be merged in when
> > > > > everything
> > > > > > works. That is not a capability we currently have.
> > > > > >
> > > > > > "This makes it impossible to release new versions of platforms
> that
> > > > would
> > > > > > be
> > > > > > usable with the same version of CLI." <--- this is a feature,
> not a
> > > > bug!
> > > > > > When we want to bump the platforms we *should* have to bump the
> CLI
> > > as
> > > > it
> > > > > > is a dependency.
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Thu, Jul 24, 2014 at 9:19 AM, Andrew Grieve <
> > agrieve@chromium.org
> > > >
> > > > > > wrote:
> > > > > >
> > > > > > > On Thu, Jul 24, 2014 at 10:40 AM, Chuck Lantz <
> > > clantz@microsoft.com>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > To me it sounds like we're talking about something bigger
> than
> > > > > pinning:
> > > > > > > > What does a Cordova version actually mean?
> > > > > > > >
> > > > > > > > When new macro-level "Cordova" features like splash screens
> and
> > > > icons
> > > > > > > > support or perhaps coming up with a way to manage code
> signing
> > > and
> > > > > > > > packaging without going into native projects are released,
> > we'll
> > > > need
> > > > > > to
> > > > > > > be
> > > > > > > > able to coordinate a release across a number of different
> > > > platforms.
> > > > > >  So,
> > > > > > > > the way I've always thought about this from and end user
> > > > perspective
> > > > > > is:
> > > > > > >
> > > > > > >
> > > > > > > Certainly having platforms at different versions will be a
> change
> > > > from
> > > > > > what
> > > > > > > we've had historically. Still, I think it will be for the
> better.
> > > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > -Updating the first digit is done for major Cordova level
> > > features
> > > > > that
> > > > > > > > affect everyone - and force everyone to change
> > > > > > > >
> > > > > > > But what if only one platform has a change that requires
> action?
> > Do
> > > > we
> > > > > > not
> > > > > > > bump the major then?, Or do we bump the major and users of
> other
> > > > > > platforms
> > > > > > > discover it doesn't actually affect them.
> > > > > > >
> > > > > > >
> > > > > > > > -Updating the second digit is about incremental improvements
> > that
> > > > > still
> > > > > > > > constitute new Cordova level features but may only support
> > > certain
> > > > > > > platforms
> > > > > > >
> > > > > > > -Updating the last digit ties to bug fixes, perf improvements,
> > and
> > > > > other
> > > > > > > > things that do not have a direct effect on end users
> > > > > > >
> > > > > > >
> > > > > > > > Two questions:
> > > > > > > > -How will documentation work if platforms go to versions
> > > > independent
> > > > > of
> > > > > > > > one another?  For example, consider this:
> > > > > > > >
> > > > > > > >         Android goes to Cordova 3.7.0 one week
> > > > > > > >         iOS goes to Cordova 3.7.0 two weeks later
> > > > > > >
> > > > > > >
> > > > > > > > Does the documentation for the same version update?
> > > > > > > >
> > > > > > >
> > > > > > > I think the easiest way is to just not version the docs. Just
> > have
> > > > them
> > > > > > > always be up-to-date for all released platforms.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > -Are we saying that there will never be shared infrastructure
> > > > across
> > > > > > > > platforms that the CLI needs?  Otherwise you could get in a
> > > > situation
> > > > > > > where
> > > > > > > > the CLI revs and only one or two platforms are actually
> > > supported.
> > > > > >  Given
> > > > > > > > Cordova really is about cross-platform/multi-device
> > development,
> > > is
> > > > > > that
> > > > > > > a
> > > > > > > > message we want to send to end users?  What about plugins?
> > > > > > > >
> > > > > > >
> > > > > > > The latest version of CLI must always support all plugins (even
> > old
> > > > > > ones),
> > > > > > > and all platform versions (even old ones). This (I believe), is
> > > > already
> > > > > > the
> > > > > > > case today, and is not too hard to maintain.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > I also think this commits the community to testing the CLI
> > > across a
> > > > > > > number
> > > > > > > > of different versions over time. The CLI would need to be
> > > validated
> > > > > > > across
> > > > > > > > a number of different major and minor versions which
> increases
> > > the
> > > > > test
> > > > > > > > burden.
> > > > > > > >
> > > > > > >
> > > > > > > I believe this to already be the case. The current workflow is:
> > > > > > >
> > > > > > > 1. Install a platform (say, android 3.2)
> > > > > > > 2. Update CLI to 3.5.0
> > > > > > > 3. CLI now expected to work with version of platform you have
> > > > > installed.
> > > > > > > 4. Decide you want to update your platform via "cordova
> platform
> > > > update
> > > > > > > android"
> > > > > > > 5. Now, your project is at android 3.5.0
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > I would argue that plugins are a potential problem right now
> -
> > > the
> > > > > > moment
> > > > > > > > a core plugin drops support for a Cordova version that people
> > are
> > > > > using
> > > > > > > > widely, I think we'll hear about it.  However, in the case
> of a
> > > > > plugin,
> > > > > > > it
> > > > > > > > is inherently multi-platform and its documentation and
> > > > functionality
> > > > > > > across
> > > > > > > > all platforms will update with one version change.  I think
> > that
> > > is
> > > > > the
> > > > > > > > issue with platforms - There needs to be a mechanism to
> > > communicate
> > > > > > that
> > > > > > > > something has changed across multiple platforms.
> > > > > > > >
> > > > > > >
> > > > > > > I think your plugin example is a great motivation for having
> > things
> > > > > > > versioned separately. If a plugin drops support for
> > android-3.0.0,
> > > > then
> > > > > > > users are free to stick with an older version of the plugin
> that
> > > does
> > > > > > > support it. I do conceded that our tooling is currently not
> great
> > > > about
> > > > > > > making this easy to do though.
> > > > > > >
> > > > > > > Plugin features almost always get added one platform at a time.
> > > > > Likewise
> > > > > > > with platform features. I don't think we should be striving to
> > add
> > > > > > features
> > > > > > > across all platforms at a time, because not all platforms even
> > have
> > > > > > people
> > > > > > > actively working on them. What's the gain in trying to
> > synchronize
> > > > > them?
> > > > > > It
> > > > > > > would only cause things to be released more slowly.
> > > > > > >
> > > > > > > For example, we recently had icons and splashscreen support
> added
> > > to
> > > > > CLI
> > > > > > > for some but not all platforms. This actually required no
> changes
> > > in
> > > > > > > platforms, because platforms already supported both. This is a
> > > great
> > > > > > > example of why we'd want CLI to not be pinned to platform
> > versions.
> > > > > > Someone
> > > > > > > running cordova-android@3.1.0 would get icon support if they
> > > updated
> > > > > > their
> > > > > > > version of CLI, and they wouldn't need to update their
> platform.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > On the Android 4.0 churn vs fixes - this sounds more like a
> > > > branching
> > > > > > > > problem that we should not pass on to end users.
> > > > > > > >
> > > > > > > > -Chuck
> > > > > > > >
> > > > > > > > -----Original Message-----
> > > > > > > > From: agrieve@google.com [mailto:agrieve@google.com] On
> Behalf
> > > Of
> > > > > > Andrew
> > > > > > > > Grieve
> > > > > > > > Sent: Thursday, July 24, 2014 6:47 AM
> > > > > > > > To: dev
> > > > > > > > Subject: Re: Proposal: remove platform versions from
> > platfroms.js
> > > > > > > >
> > > > > > > > I agree that the feature will make installing platforms less
> > > > > > > predictable...
> > > > > > > > or at least, just as unpredictable as plugins.
> > > > > > > >
> > > > > > > > It is a good idea to look at exactly what the benefits are
> > > though.
> > > > > > > >
> > > > > > > > First - the benefits of removing the idea of a "cadence
> > version":
> > > > > > > > - Android 4.0 is on the horizon, maybe iOS 4.0 as well. Does
> > this
> > > > > mean
> > > > > > > > that when they are ready, we should force all platforms to
> jump
> > > to
> > > > > 4.0?
> > > > > > > > Wouldn't be too bad...
> > > > > > > > - But once at 4.0, what if Windows or Blackberry requires a
> > major
> > > > > > release
> > > > > > > > a couple months later, move all platforms to 5.0?
> > > > > > > > - What if Android undergoes a lot of churn come 4.0, and
> wants
> > to
> > > > do
> > > > > 3
> > > > > > > > more bugfix releases within the first month after? Do we
> force
> > > all
> > > > > > > > platform's versions to be updated? If not, what does the
> > cadence
> > > > > number
> > > > > > > on
> > > > > > > > CLI look like?
> > > > > > > > - Cadence versioning forces us to try and release multiple
> > > > platforms
> > > > > at
> > > > > > > > the same time.
> > > > > > > >   - E.g. Jesse wants to release windows, but has been waiting
> > for
> > > > > > Android
> > > > > > > > to be ready.
> > > > > > > >   - If each platform just released when it was ready, and had
> > > > > separate
> > > > > > > > blog posts, I think we'd have a happier release process, and
> > > would
> > > > > > > release
> > > > > > > > more often.
> > > > > > > >
> > > > > > > > Now, we could do away with cadence version and still have CLI
> > use
> > > > the
> > > > > > > > version in its platforms.js file for each platform. So what
> > does
> > > > this
> > > > > > > > specific change of removing the pinning buy us?
> > > > > > > > - It will lighten the load of doing platform releases.
> > > > > > > > - It will make platforms and plugins both work in the same
> way.
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > On Wed, Jul 23, 2014 at 2:49 PM, Jesse <
> > purplecabbage@gmail.com>
> > > > > > wrote:
> > > > > > > >
> > > > > > > > > I agree, there are many cases where this will lead to
> > complete
> > > > > > > > > un-predictability, and it is still unclear who this
> 'feature'
> > > > > > benefits.
> > > > > > > > >
> > > > > > > > > How can we guarantee that latest version of a newly added
> > > > platform
> > > > > > > > > supports all the same plugins of the previously added
> > > platforms?
> > > > > > > > >
> > > > > > > > > I think ultimately the only benefit is to give us some
> > > > flexibility
> > > > > > > > > with release schedules, but I would much rather have us
> focus
> > > on
> > > > > just
> > > > > > > > > releasing everything more often.  Historically we have
> never
> > > been
> > > > > > able
> > > > > > > > > to deliver a patched point release in under a month, so
> > > assuming
> > > > we
> > > > > > > > > can get back to releasing every month, all would be fine,
> and
> > > the
> > > > > > > > > train could just keep rolling forwards. Predictably!
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > @purplecabbage
> > > > > > > > > risingj.com
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On Wed, Jul 23, 2014 at 10:59 AM, Parashuram Narasimhan (MS
> > > OPEN
> > > > > > TECH)
> > > > > > > > > < panarasi@microsoft.com> wrote:
> > > > > > > > >
> > > > > > > > > > I was thinking platforms are devDependencies and plugins
> > are
> > > > > > > > > > dependencies
> > > > > > > > > > :)
> > > > > > > > > >
> > > > > > > > > > In a way, that’s how the bundling works - plugins are
> > > packaged
> > > > > with
> > > > > > > > > > the app, while platforms are only needed during
> development
> > > !!
> > > > > > > > > >
> > > > > > > > > > -----Original Message-----
> > > > > > > > > > From: Anis KADRI [mailto:anis.kadri@gmail.com]
> > > > > > > > > > Sent: Wednesday, July 23, 2014 10:54 AM
> > > > > > > > > > To: dev@cordova.apache.org
> > > > > > > > > > Subject: Re: Proposal: remove platform versions from
> > > > platfroms.js
> > > > > > > > > >
> > > > > > > > > > +1 for package.json for platforms. plugins might a bit
> > > trickier
> > > > > but
> > > > > > > > > > +still
> > > > > > > > > > doable, we could get rid of plugins/ but we somehow need
> to
> > > > keep
> > > > > > > > > > track of them in node_modules/ (maybe use one of the 10
> > > config
> > > > > > files
> > > > > > > > we have).
> > > > > > > > > > Platforms in package.json should cause no problems
> though,
> > > > > > > > > > add/remove platforms, pin/unpin versions if required.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > On Wed, Jul 23, 2014 at 7:36 AM, Michal Mocny <
> > > > > mmocny@chromium.org
> > > > > > >
> > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > This sounds like a great topic for hangout Friday.
>  Glad
> > to
> > > > > have
> > > > > > a
> > > > > > > > > > > concrete proposal / some counter arguments to discuss.
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > On Wed, Jul 23, 2014 at 10:22 AM, Mark Koudritsky
> > > > > > > > > > > <ka...@google.com>
> > > > > > > > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > Currently WebWorks ships specific versions of
> things.
> > > > > > > > > > > > > If we had shipped unpinned versions of stuff, then
> > > > > eventually
> > > > > > > > > > > > > we would have created projects which our UI
> wouldn't
> > > have
> > > > > > > > > > > > > recognized as valid (because, they e.g. Didn't
> have a
> > > > > > > > > > > > > ".cordova", or a "hooks", or a
> > > > > > > > > > > "merges"
> > > > > > > > > > > > > or whichever things we had been using to determine
> > if a
> > > > > > > > > > > > > project was
> > > > > > > > > > > > valid).
> > > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > As long as you continue to ship a version of
> > > > > cordova-backberry
> > > > > > > > > > > > bundled
> > > > > > > > > > > with
> > > > > > > > > > > > WebWorks, it won't be affected by the change I
> propose.
> > > CLI
> > > > > > will
> > > > > > > > > > > > use that bundled version just like it does now using
> > the
> > > > > > > > > > > > settings in .cordova/config.json. We do the same
> thing
> > > with
> > > > > > cca.
> > > > > > > > > > > >
> > > > > > > > > > > > If in the future you decide to stop bundling
> > > > > cordova-blackberry
> > > > > > > > > > > > with WebWorks and switch to the npm published
> > versions, I
> > > > see
> > > > > > > > > > > > several good
> > > > > > > > > > > ways
> > > > > > > > > > > > for doing that, but in any case, you will probably
> want
> > > to
> > > > > > > > > > > > expose the version (or range of versions) to use as a
> > > user
> > > > > > > > editable setting.
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: Proposal: remove platform versions from platfroms.js

Posted by Brian LeRoux <b...@brian.io>.
- ya I don't care at all about whatever we want the versioning scheme to be

I don't see much benefit from this:

"cordova platform add android@NEXT_VERSION"

I'd rather see ppl update their tool to the next version of the CLI.




On Thu, Jul 24, 2014 at 12:36 PM, Andrew Grieve <ag...@chromium.org>
wrote:

> How about discussing dropping the CAD-SEM version of CLI, and just have
> SEM?
>
> Probably it'd still be good to go over what *exactly* the platform release
> process should look like. E.g.:
> - Any platform can be released at any time
> - If it requires an update to cordova.js, then create a new cordova.js
> version.
> - Create a blog post just for your platform
> - Tell users to try it out via "cordova platform add android@NEXT_VERSION"
> - Next time tools release happens, CLI will have its default platform
> version updated to include the new platform release.
>
>
> On Thu, Jul 24, 2014 at 3:18 PM, Michal Mocny <mm...@chromium.org> wrote:
>
> > OOOOhhh, Brain you meant cordova-cli's package.json, not the project
> > workspaces!  I like that.  I like that you can create a project while
> > offline that way.  I'm also with David/Brian/Others that CLI can have a
> > default pinned version set, yet we still get cordova platform version
> > independance.
> >
> > I thought we were proposing creating a package.json as part of "cordova
> > create" alongside config.xml, which I was really O_o about.  (I think
> this
> > is a likely direction we may end up, but not just nilly willy).
> >
> > Glad we are coming to agreement, but now we wont have anything to discuss
> > Friday ;)
> >
> > -Michal
> >
> >
> > On Thu, Jul 24, 2014 at 2:56 PM, Brian LeRoux <b...@brian.io> wrote:
> >
> > > totally agree. the cli package.json can capture which versions of the
> > > platforms it needs. the platforms can release with reckless abandon
> > >
> > > (maybe we'll even hit THREE times this year! ;)
> > >
> > >
> > > On Thu, Jul 24, 2014 at 11:17 AM, David Kemp <dr...@chromium.org>
> > wrote:
> > >
> > > > It seems to me that:
> > > > 1) to make our users happy and get them to consider using newer
> > versions,
> > > > we need to have the perception of stability. Nice clean, well tested,
> > > > co-ordinated releases are a good way to get that. For that reason, I
> > > think
> > > > a method of providing a 'pinned' release set for the end user is a
> good
> > > way
> > > > to deliver that.
> > > > 2) to make it easy and fast for the various platform contributors to
> > > > release new stuff, we need independent platform versioning. That
> would
> > > > allow platforms to move ahead separately - as long as all tooling is
> > > > backward compatible.
> > > >
> > > > We should be able to do both.
> > > >
> > > >
> > > >
> > > > On Thu, Jul 24, 2014 at 1:38 PM, Brian LeRoux <b...@brian.io> wrote:
> > > >
> > > > > I am against this change. I am in favor of adding platforms via
> > > > > package.json, however.
> > > > >
> > > > > We need to version lock our dependencies in the CLI. Testing and
> bug
> > > > > resolution will be impossible otherwise. (We did this for that
> > reason.)
> > > > > However, the Platforms don't need to be synchronized. Platforms can
> > > > release
> > > > > as they want and the CLI can pick them up as needs be BUT the
> > > versioning
> > > > of
> > > > > dependencies needs to be explicit.
> > > > >
> > > > > The only way 'always grab latest' works is when master is pristine
> > and
> > > > all
> > > > > development happens on topic branches only to be merged in when
> > > > everything
> > > > > works. That is not a capability we currently have.
> > > > >
> > > > > "This makes it impossible to release new versions of platforms that
> > > would
> > > > > be
> > > > > usable with the same version of CLI." <--- this is a feature, not a
> > > bug!
> > > > > When we want to bump the platforms we *should* have to bump the CLI
> > as
> > > it
> > > > > is a dependency.
> > > > >
> > > > >
> > > > >
> > > > > On Thu, Jul 24, 2014 at 9:19 AM, Andrew Grieve <
> agrieve@chromium.org
> > >
> > > > > wrote:
> > > > >
> > > > > > On Thu, Jul 24, 2014 at 10:40 AM, Chuck Lantz <
> > clantz@microsoft.com>
> > > > > > wrote:
> > > > > >
> > > > > > > To me it sounds like we're talking about something bigger than
> > > > pinning:
> > > > > > > What does a Cordova version actually mean?
> > > > > > >
> > > > > > > When new macro-level "Cordova" features like splash screens and
> > > icons
> > > > > > > support or perhaps coming up with a way to manage code signing
> > and
> > > > > > > packaging without going into native projects are released,
> we'll
> > > need
> > > > > to
> > > > > > be
> > > > > > > able to coordinate a release across a number of different
> > > platforms.
> > > > >  So,
> > > > > > > the way I've always thought about this from and end user
> > > perspective
> > > > > is:
> > > > > >
> > > > > >
> > > > > > Certainly having platforms at different versions will be a change
> > > from
> > > > > what
> > > > > > we've had historically. Still, I think it will be for the better.
> > > > > >
> > > > > >
> > > > > > >
> > > > > > > -Updating the first digit is done for major Cordova level
> > features
> > > > that
> > > > > > > affect everyone - and force everyone to change
> > > > > > >
> > > > > > But what if only one platform has a change that requires action?
> Do
> > > we
> > > > > not
> > > > > > bump the major then?, Or do we bump the major and users of other
> > > > > platforms
> > > > > > discover it doesn't actually affect them.
> > > > > >
> > > > > >
> > > > > > > -Updating the second digit is about incremental improvements
> that
> > > > still
> > > > > > > constitute new Cordova level features but may only support
> > certain
> > > > > > platforms
> > > > > >
> > > > > > -Updating the last digit ties to bug fixes, perf improvements,
> and
> > > > other
> > > > > > > things that do not have a direct effect on end users
> > > > > >
> > > > > >
> > > > > > > Two questions:
> > > > > > > -How will documentation work if platforms go to versions
> > > independent
> > > > of
> > > > > > > one another?  For example, consider this:
> > > > > > >
> > > > > > >         Android goes to Cordova 3.7.0 one week
> > > > > > >         iOS goes to Cordova 3.7.0 two weeks later
> > > > > >
> > > > > >
> > > > > > > Does the documentation for the same version update?
> > > > > > >
> > > > > >
> > > > > > I think the easiest way is to just not version the docs. Just
> have
> > > them
> > > > > > always be up-to-date for all released platforms.
> > > > > >
> > > > > >
> > > > > >
> > > > > > >
> > > > > > > -Are we saying that there will never be shared infrastructure
> > > across
> > > > > > > platforms that the CLI needs?  Otherwise you could get in a
> > > situation
> > > > > > where
> > > > > > > the CLI revs and only one or two platforms are actually
> > supported.
> > > > >  Given
> > > > > > > Cordova really is about cross-platform/multi-device
> development,
> > is
> > > > > that
> > > > > > a
> > > > > > > message we want to send to end users?  What about plugins?
> > > > > > >
> > > > > >
> > > > > > The latest version of CLI must always support all plugins (even
> old
> > > > > ones),
> > > > > > and all platform versions (even old ones). This (I believe), is
> > > already
> > > > > the
> > > > > > case today, and is not too hard to maintain.
> > > > > >
> > > > > >
> > > > > >
> > > > > > >
> > > > > > > I also think this commits the community to testing the CLI
> > across a
> > > > > > number
> > > > > > > of different versions over time. The CLI would need to be
> > validated
> > > > > > across
> > > > > > > a number of different major and minor versions which increases
> > the
> > > > test
> > > > > > > burden.
> > > > > > >
> > > > > >
> > > > > > I believe this to already be the case. The current workflow is:
> > > > > >
> > > > > > 1. Install a platform (say, android 3.2)
> > > > > > 2. Update CLI to 3.5.0
> > > > > > 3. CLI now expected to work with version of platform you have
> > > > installed.
> > > > > > 4. Decide you want to update your platform via "cordova platform
> > > update
> > > > > > android"
> > > > > > 5. Now, your project is at android 3.5.0
> > > > > >
> > > > > >
> > > > > >
> > > > > > >
> > > > > > > I would argue that plugins are a potential problem right now -
> > the
> > > > > moment
> > > > > > > a core plugin drops support for a Cordova version that people
> are
> > > > using
> > > > > > > widely, I think we'll hear about it.  However, in the case of a
> > > > plugin,
> > > > > > it
> > > > > > > is inherently multi-platform and its documentation and
> > > functionality
> > > > > > across
> > > > > > > all platforms will update with one version change.  I think
> that
> > is
> > > > the
> > > > > > > issue with platforms - There needs to be a mechanism to
> > communicate
> > > > > that
> > > > > > > something has changed across multiple platforms.
> > > > > > >
> > > > > >
> > > > > > I think your plugin example is a great motivation for having
> things
> > > > > > versioned separately. If a plugin drops support for
> android-3.0.0,
> > > then
> > > > > > users are free to stick with an older version of the plugin that
> > does
> > > > > > support it. I do conceded that our tooling is currently not great
> > > about
> > > > > > making this easy to do though.
> > > > > >
> > > > > > Plugin features almost always get added one platform at a time.
> > > > Likewise
> > > > > > with platform features. I don't think we should be striving to
> add
> > > > > features
> > > > > > across all platforms at a time, because not all platforms even
> have
> > > > > people
> > > > > > actively working on them. What's the gain in trying to
> synchronize
> > > > them?
> > > > > It
> > > > > > would only cause things to be released more slowly.
> > > > > >
> > > > > > For example, we recently had icons and splashscreen support added
> > to
> > > > CLI
> > > > > > for some but not all platforms. This actually required no changes
> > in
> > > > > > platforms, because platforms already supported both. This is a
> > great
> > > > > > example of why we'd want CLI to not be pinned to platform
> versions.
> > > > > Someone
> > > > > > running cordova-android@3.1.0 would get icon support if they
> > updated
> > > > > their
> > > > > > version of CLI, and they wouldn't need to update their platform.
> > > > > >
> > > > > >
> > > > > >
> > > > > > >
> > > > > > > On the Android 4.0 churn vs fixes - this sounds more like a
> > > branching
> > > > > > > problem that we should not pass on to end users.
> > > > > > >
> > > > > > > -Chuck
> > > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: agrieve@google.com [mailto:agrieve@google.com] On Behalf
> > Of
> > > > > Andrew
> > > > > > > Grieve
> > > > > > > Sent: Thursday, July 24, 2014 6:47 AM
> > > > > > > To: dev
> > > > > > > Subject: Re: Proposal: remove platform versions from
> platfroms.js
> > > > > > >
> > > > > > > I agree that the feature will make installing platforms less
> > > > > > predictable...
> > > > > > > or at least, just as unpredictable as plugins.
> > > > > > >
> > > > > > > It is a good idea to look at exactly what the benefits are
> > though.
> > > > > > >
> > > > > > > First - the benefits of removing the idea of a "cadence
> version":
> > > > > > > - Android 4.0 is on the horizon, maybe iOS 4.0 as well. Does
> this
> > > > mean
> > > > > > > that when they are ready, we should force all platforms to jump
> > to
> > > > 4.0?
> > > > > > > Wouldn't be too bad...
> > > > > > > - But once at 4.0, what if Windows or Blackberry requires a
> major
> > > > > release
> > > > > > > a couple months later, move all platforms to 5.0?
> > > > > > > - What if Android undergoes a lot of churn come 4.0, and wants
> to
> > > do
> > > > 3
> > > > > > > more bugfix releases within the first month after? Do we force
> > all
> > > > > > > platform's versions to be updated? If not, what does the
> cadence
> > > > number
> > > > > > on
> > > > > > > CLI look like?
> > > > > > > - Cadence versioning forces us to try and release multiple
> > > platforms
> > > > at
> > > > > > > the same time.
> > > > > > >   - E.g. Jesse wants to release windows, but has been waiting
> for
> > > > > Android
> > > > > > > to be ready.
> > > > > > >   - If each platform just released when it was ready, and had
> > > > separate
> > > > > > > blog posts, I think we'd have a happier release process, and
> > would
> > > > > > release
> > > > > > > more often.
> > > > > > >
> > > > > > > Now, we could do away with cadence version and still have CLI
> use
> > > the
> > > > > > > version in its platforms.js file for each platform. So what
> does
> > > this
> > > > > > > specific change of removing the pinning buy us?
> > > > > > > - It will lighten the load of doing platform releases.
> > > > > > > - It will make platforms and plugins both work in the same way.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On Wed, Jul 23, 2014 at 2:49 PM, Jesse <
> purplecabbage@gmail.com>
> > > > > wrote:
> > > > > > >
> > > > > > > > I agree, there are many cases where this will lead to
> complete
> > > > > > > > un-predictability, and it is still unclear who this 'feature'
> > > > > benefits.
> > > > > > > >
> > > > > > > > How can we guarantee that latest version of a newly added
> > > platform
> > > > > > > > supports all the same plugins of the previously added
> > platforms?
> > > > > > > >
> > > > > > > > I think ultimately the only benefit is to give us some
> > > flexibility
> > > > > > > > with release schedules, but I would much rather have us focus
> > on
> > > > just
> > > > > > > > releasing everything more often.  Historically we have never
> > been
> > > > > able
> > > > > > > > to deliver a patched point release in under a month, so
> > assuming
> > > we
> > > > > > > > can get back to releasing every month, all would be fine, and
> > the
> > > > > > > > train could just keep rolling forwards. Predictably!
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > @purplecabbage
> > > > > > > > risingj.com
> > > > > > > >
> > > > > > > >
> > > > > > > > On Wed, Jul 23, 2014 at 10:59 AM, Parashuram Narasimhan (MS
> > OPEN
> > > > > TECH)
> > > > > > > > < panarasi@microsoft.com> wrote:
> > > > > > > >
> > > > > > > > > I was thinking platforms are devDependencies and plugins
> are
> > > > > > > > > dependencies
> > > > > > > > > :)
> > > > > > > > >
> > > > > > > > > In a way, that’s how the bundling works - plugins are
> > packaged
> > > > with
> > > > > > > > > the app, while platforms are only needed during development
> > !!
> > > > > > > > >
> > > > > > > > > -----Original Message-----
> > > > > > > > > From: Anis KADRI [mailto:anis.kadri@gmail.com]
> > > > > > > > > Sent: Wednesday, July 23, 2014 10:54 AM
> > > > > > > > > To: dev@cordova.apache.org
> > > > > > > > > Subject: Re: Proposal: remove platform versions from
> > > platfroms.js
> > > > > > > > >
> > > > > > > > > +1 for package.json for platforms. plugins might a bit
> > trickier
> > > > but
> > > > > > > > > +still
> > > > > > > > > doable, we could get rid of plugins/ but we somehow need to
> > > keep
> > > > > > > > > track of them in node_modules/ (maybe use one of the 10
> > config
> > > > > files
> > > > > > > we have).
> > > > > > > > > Platforms in package.json should cause no problems though,
> > > > > > > > > add/remove platforms, pin/unpin versions if required.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On Wed, Jul 23, 2014 at 7:36 AM, Michal Mocny <
> > > > mmocny@chromium.org
> > > > > >
> > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > This sounds like a great topic for hangout Friday.  Glad
> to
> > > > have
> > > > > a
> > > > > > > > > > concrete proposal / some counter arguments to discuss.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > On Wed, Jul 23, 2014 at 10:22 AM, Mark Koudritsky
> > > > > > > > > > <ka...@google.com>
> > > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > Currently WebWorks ships specific versions of things.
> > > > > > > > > > > > If we had shipped unpinned versions of stuff, then
> > > > eventually
> > > > > > > > > > > > we would have created projects which our UI wouldn't
> > have
> > > > > > > > > > > > recognized as valid (because, they e.g. Didn't have a
> > > > > > > > > > > > ".cordova", or a "hooks", or a
> > > > > > > > > > "merges"
> > > > > > > > > > > > or whichever things we had been using to determine
> if a
> > > > > > > > > > > > project was
> > > > > > > > > > > valid).
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > As long as you continue to ship a version of
> > > > cordova-backberry
> > > > > > > > > > > bundled
> > > > > > > > > > with
> > > > > > > > > > > WebWorks, it won't be affected by the change I propose.
> > CLI
> > > > > will
> > > > > > > > > > > use that bundled version just like it does now using
> the
> > > > > > > > > > > settings in .cordova/config.json. We do the same thing
> > with
> > > > > cca.
> > > > > > > > > > >
> > > > > > > > > > > If in the future you decide to stop bundling
> > > > cordova-blackberry
> > > > > > > > > > > with WebWorks and switch to the npm published
> versions, I
> > > see
> > > > > > > > > > > several good
> > > > > > > > > > ways
> > > > > > > > > > > for doing that, but in any case, you will probably want
> > to
> > > > > > > > > > > expose the version (or range of versions) to use as a
> > user
> > > > > > > editable setting.
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: Proposal: remove platform versions from platfroms.js

Posted by Andrew Grieve <ag...@chromium.org>.
How about discussing dropping the CAD-SEM version of CLI, and just have SEM?

Probably it'd still be good to go over what *exactly* the platform release
process should look like. E.g.:
- Any platform can be released at any time
- If it requires an update to cordova.js, then create a new cordova.js
version.
- Create a blog post just for your platform
- Tell users to try it out via "cordova platform add android@NEXT_VERSION"
- Next time tools release happens, CLI will have its default platform
version updated to include the new platform release.


On Thu, Jul 24, 2014 at 3:18 PM, Michal Mocny <mm...@chromium.org> wrote:

> OOOOhhh, Brain you meant cordova-cli's package.json, not the project
> workspaces!  I like that.  I like that you can create a project while
> offline that way.  I'm also with David/Brian/Others that CLI can have a
> default pinned version set, yet we still get cordova platform version
> independance.
>
> I thought we were proposing creating a package.json as part of "cordova
> create" alongside config.xml, which I was really O_o about.  (I think this
> is a likely direction we may end up, but not just nilly willy).
>
> Glad we are coming to agreement, but now we wont have anything to discuss
> Friday ;)
>
> -Michal
>
>
> On Thu, Jul 24, 2014 at 2:56 PM, Brian LeRoux <b...@brian.io> wrote:
>
> > totally agree. the cli package.json can capture which versions of the
> > platforms it needs. the platforms can release with reckless abandon
> >
> > (maybe we'll even hit THREE times this year! ;)
> >
> >
> > On Thu, Jul 24, 2014 at 11:17 AM, David Kemp <dr...@chromium.org>
> wrote:
> >
> > > It seems to me that:
> > > 1) to make our users happy and get them to consider using newer
> versions,
> > > we need to have the perception of stability. Nice clean, well tested,
> > > co-ordinated releases are a good way to get that. For that reason, I
> > think
> > > a method of providing a 'pinned' release set for the end user is a good
> > way
> > > to deliver that.
> > > 2) to make it easy and fast for the various platform contributors to
> > > release new stuff, we need independent platform versioning. That would
> > > allow platforms to move ahead separately - as long as all tooling is
> > > backward compatible.
> > >
> > > We should be able to do both.
> > >
> > >
> > >
> > > On Thu, Jul 24, 2014 at 1:38 PM, Brian LeRoux <b...@brian.io> wrote:
> > >
> > > > I am against this change. I am in favor of adding platforms via
> > > > package.json, however.
> > > >
> > > > We need to version lock our dependencies in the CLI. Testing and bug
> > > > resolution will be impossible otherwise. (We did this for that
> reason.)
> > > > However, the Platforms don't need to be synchronized. Platforms can
> > > release
> > > > as they want and the CLI can pick them up as needs be BUT the
> > versioning
> > > of
> > > > dependencies needs to be explicit.
> > > >
> > > > The only way 'always grab latest' works is when master is pristine
> and
> > > all
> > > > development happens on topic branches only to be merged in when
> > > everything
> > > > works. That is not a capability we currently have.
> > > >
> > > > "This makes it impossible to release new versions of platforms that
> > would
> > > > be
> > > > usable with the same version of CLI." <--- this is a feature, not a
> > bug!
> > > > When we want to bump the platforms we *should* have to bump the CLI
> as
> > it
> > > > is a dependency.
> > > >
> > > >
> > > >
> > > > On Thu, Jul 24, 2014 at 9:19 AM, Andrew Grieve <agrieve@chromium.org
> >
> > > > wrote:
> > > >
> > > > > On Thu, Jul 24, 2014 at 10:40 AM, Chuck Lantz <
> clantz@microsoft.com>
> > > > > wrote:
> > > > >
> > > > > > To me it sounds like we're talking about something bigger than
> > > pinning:
> > > > > > What does a Cordova version actually mean?
> > > > > >
> > > > > > When new macro-level "Cordova" features like splash screens and
> > icons
> > > > > > support or perhaps coming up with a way to manage code signing
> and
> > > > > > packaging without going into native projects are released, we'll
> > need
> > > > to
> > > > > be
> > > > > > able to coordinate a release across a number of different
> > platforms.
> > > >  So,
> > > > > > the way I've always thought about this from and end user
> > perspective
> > > > is:
> > > > >
> > > > >
> > > > > Certainly having platforms at different versions will be a change
> > from
> > > > what
> > > > > we've had historically. Still, I think it will be for the better.
> > > > >
> > > > >
> > > > > >
> > > > > > -Updating the first digit is done for major Cordova level
> features
> > > that
> > > > > > affect everyone - and force everyone to change
> > > > > >
> > > > > But what if only one platform has a change that requires action? Do
> > we
> > > > not
> > > > > bump the major then?, Or do we bump the major and users of other
> > > > platforms
> > > > > discover it doesn't actually affect them.
> > > > >
> > > > >
> > > > > > -Updating the second digit is about incremental improvements that
> > > still
> > > > > > constitute new Cordova level features but may only support
> certain
> > > > > platforms
> > > > >
> > > > > -Updating the last digit ties to bug fixes, perf improvements, and
> > > other
> > > > > > things that do not have a direct effect on end users
> > > > >
> > > > >
> > > > > > Two questions:
> > > > > > -How will documentation work if platforms go to versions
> > independent
> > > of
> > > > > > one another?  For example, consider this:
> > > > > >
> > > > > >         Android goes to Cordova 3.7.0 one week
> > > > > >         iOS goes to Cordova 3.7.0 two weeks later
> > > > >
> > > > >
> > > > > > Does the documentation for the same version update?
> > > > > >
> > > > >
> > > > > I think the easiest way is to just not version the docs. Just have
> > them
> > > > > always be up-to-date for all released platforms.
> > > > >
> > > > >
> > > > >
> > > > > >
> > > > > > -Are we saying that there will never be shared infrastructure
> > across
> > > > > > platforms that the CLI needs?  Otherwise you could get in a
> > situation
> > > > > where
> > > > > > the CLI revs and only one or two platforms are actually
> supported.
> > > >  Given
> > > > > > Cordova really is about cross-platform/multi-device development,
> is
> > > > that
> > > > > a
> > > > > > message we want to send to end users?  What about plugins?
> > > > > >
> > > > >
> > > > > The latest version of CLI must always support all plugins (even old
> > > > ones),
> > > > > and all platform versions (even old ones). This (I believe), is
> > already
> > > > the
> > > > > case today, and is not too hard to maintain.
> > > > >
> > > > >
> > > > >
> > > > > >
> > > > > > I also think this commits the community to testing the CLI
> across a
> > > > > number
> > > > > > of different versions over time. The CLI would need to be
> validated
> > > > > across
> > > > > > a number of different major and minor versions which increases
> the
> > > test
> > > > > > burden.
> > > > > >
> > > > >
> > > > > I believe this to already be the case. The current workflow is:
> > > > >
> > > > > 1. Install a platform (say, android 3.2)
> > > > > 2. Update CLI to 3.5.0
> > > > > 3. CLI now expected to work with version of platform you have
> > > installed.
> > > > > 4. Decide you want to update your platform via "cordova platform
> > update
> > > > > android"
> > > > > 5. Now, your project is at android 3.5.0
> > > > >
> > > > >
> > > > >
> > > > > >
> > > > > > I would argue that plugins are a potential problem right now -
> the
> > > > moment
> > > > > > a core plugin drops support for a Cordova version that people are
> > > using
> > > > > > widely, I think we'll hear about it.  However, in the case of a
> > > plugin,
> > > > > it
> > > > > > is inherently multi-platform and its documentation and
> > functionality
> > > > > across
> > > > > > all platforms will update with one version change.  I think that
> is
> > > the
> > > > > > issue with platforms - There needs to be a mechanism to
> communicate
> > > > that
> > > > > > something has changed across multiple platforms.
> > > > > >
> > > > >
> > > > > I think your plugin example is a great motivation for having things
> > > > > versioned separately. If a plugin drops support for android-3.0.0,
> > then
> > > > > users are free to stick with an older version of the plugin that
> does
> > > > > support it. I do conceded that our tooling is currently not great
> > about
> > > > > making this easy to do though.
> > > > >
> > > > > Plugin features almost always get added one platform at a time.
> > > Likewise
> > > > > with platform features. I don't think we should be striving to add
> > > > features
> > > > > across all platforms at a time, because not all platforms even have
> > > > people
> > > > > actively working on them. What's the gain in trying to synchronize
> > > them?
> > > > It
> > > > > would only cause things to be released more slowly.
> > > > >
> > > > > For example, we recently had icons and splashscreen support added
> to
> > > CLI
> > > > > for some but not all platforms. This actually required no changes
> in
> > > > > platforms, because platforms already supported both. This is a
> great
> > > > > example of why we'd want CLI to not be pinned to platform versions.
> > > > Someone
> > > > > running cordova-android@3.1.0 would get icon support if they
> updated
> > > > their
> > > > > version of CLI, and they wouldn't need to update their platform.
> > > > >
> > > > >
> > > > >
> > > > > >
> > > > > > On the Android 4.0 churn vs fixes - this sounds more like a
> > branching
> > > > > > problem that we should not pass on to end users.
> > > > > >
> > > > > > -Chuck
> > > > > >
> > > > > > -----Original Message-----
> > > > > > From: agrieve@google.com [mailto:agrieve@google.com] On Behalf
> Of
> > > > Andrew
> > > > > > Grieve
> > > > > > Sent: Thursday, July 24, 2014 6:47 AM
> > > > > > To: dev
> > > > > > Subject: Re: Proposal: remove platform versions from platfroms.js
> > > > > >
> > > > > > I agree that the feature will make installing platforms less
> > > > > predictable...
> > > > > > or at least, just as unpredictable as plugins.
> > > > > >
> > > > > > It is a good idea to look at exactly what the benefits are
> though.
> > > > > >
> > > > > > First - the benefits of removing the idea of a "cadence version":
> > > > > > - Android 4.0 is on the horizon, maybe iOS 4.0 as well. Does this
> > > mean
> > > > > > that when they are ready, we should force all platforms to jump
> to
> > > 4.0?
> > > > > > Wouldn't be too bad...
> > > > > > - But once at 4.0, what if Windows or Blackberry requires a major
> > > > release
> > > > > > a couple months later, move all platforms to 5.0?
> > > > > > - What if Android undergoes a lot of churn come 4.0, and wants to
> > do
> > > 3
> > > > > > more bugfix releases within the first month after? Do we force
> all
> > > > > > platform's versions to be updated? If not, what does the cadence
> > > number
> > > > > on
> > > > > > CLI look like?
> > > > > > - Cadence versioning forces us to try and release multiple
> > platforms
> > > at
> > > > > > the same time.
> > > > > >   - E.g. Jesse wants to release windows, but has been waiting for
> > > > Android
> > > > > > to be ready.
> > > > > >   - If each platform just released when it was ready, and had
> > > separate
> > > > > > blog posts, I think we'd have a happier release process, and
> would
> > > > > release
> > > > > > more often.
> > > > > >
> > > > > > Now, we could do away with cadence version and still have CLI use
> > the
> > > > > > version in its platforms.js file for each platform. So what does
> > this
> > > > > > specific change of removing the pinning buy us?
> > > > > > - It will lighten the load of doing platform releases.
> > > > > > - It will make platforms and plugins both work in the same way.
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Wed, Jul 23, 2014 at 2:49 PM, Jesse <pu...@gmail.com>
> > > > wrote:
> > > > > >
> > > > > > > I agree, there are many cases where this will lead to complete
> > > > > > > un-predictability, and it is still unclear who this 'feature'
> > > > benefits.
> > > > > > >
> > > > > > > How can we guarantee that latest version of a newly added
> > platform
> > > > > > > supports all the same plugins of the previously added
> platforms?
> > > > > > >
> > > > > > > I think ultimately the only benefit is to give us some
> > flexibility
> > > > > > > with release schedules, but I would much rather have us focus
> on
> > > just
> > > > > > > releasing everything more often.  Historically we have never
> been
> > > > able
> > > > > > > to deliver a patched point release in under a month, so
> assuming
> > we
> > > > > > > can get back to releasing every month, all would be fine, and
> the
> > > > > > > train could just keep rolling forwards. Predictably!
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > @purplecabbage
> > > > > > > risingj.com
> > > > > > >
> > > > > > >
> > > > > > > On Wed, Jul 23, 2014 at 10:59 AM, Parashuram Narasimhan (MS
> OPEN
> > > > TECH)
> > > > > > > < panarasi@microsoft.com> wrote:
> > > > > > >
> > > > > > > > I was thinking platforms are devDependencies and plugins are
> > > > > > > > dependencies
> > > > > > > > :)
> > > > > > > >
> > > > > > > > In a way, that’s how the bundling works - plugins are
> packaged
> > > with
> > > > > > > > the app, while platforms are only needed during development
> !!
> > > > > > > >
> > > > > > > > -----Original Message-----
> > > > > > > > From: Anis KADRI [mailto:anis.kadri@gmail.com]
> > > > > > > > Sent: Wednesday, July 23, 2014 10:54 AM
> > > > > > > > To: dev@cordova.apache.org
> > > > > > > > Subject: Re: Proposal: remove platform versions from
> > platfroms.js
> > > > > > > >
> > > > > > > > +1 for package.json for platforms. plugins might a bit
> trickier
> > > but
> > > > > > > > +still
> > > > > > > > doable, we could get rid of plugins/ but we somehow need to
> > keep
> > > > > > > > track of them in node_modules/ (maybe use one of the 10
> config
> > > > files
> > > > > > we have).
> > > > > > > > Platforms in package.json should cause no problems though,
> > > > > > > > add/remove platforms, pin/unpin versions if required.
> > > > > > > >
> > > > > > > >
> > > > > > > > On Wed, Jul 23, 2014 at 7:36 AM, Michal Mocny <
> > > mmocny@chromium.org
> > > > >
> > > > > > > wrote:
> > > > > > > >
> > > > > > > > > This sounds like a great topic for hangout Friday.  Glad to
> > > have
> > > > a
> > > > > > > > > concrete proposal / some counter arguments to discuss.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On Wed, Jul 23, 2014 at 10:22 AM, Mark Koudritsky
> > > > > > > > > <ka...@google.com>
> > > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > Currently WebWorks ships specific versions of things.
> > > > > > > > > > > If we had shipped unpinned versions of stuff, then
> > > eventually
> > > > > > > > > > > we would have created projects which our UI wouldn't
> have
> > > > > > > > > > > recognized as valid (because, they e.g. Didn't have a
> > > > > > > > > > > ".cordova", or a "hooks", or a
> > > > > > > > > "merges"
> > > > > > > > > > > or whichever things we had been using to determine if a
> > > > > > > > > > > project was
> > > > > > > > > > valid).
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > As long as you continue to ship a version of
> > > cordova-backberry
> > > > > > > > > > bundled
> > > > > > > > > with
> > > > > > > > > > WebWorks, it won't be affected by the change I propose.
> CLI
> > > > will
> > > > > > > > > > use that bundled version just like it does now using the
> > > > > > > > > > settings in .cordova/config.json. We do the same thing
> with
> > > > cca.
> > > > > > > > > >
> > > > > > > > > > If in the future you decide to stop bundling
> > > cordova-blackberry
> > > > > > > > > > with WebWorks and switch to the npm published versions, I
> > see
> > > > > > > > > > several good
> > > > > > > > > ways
> > > > > > > > > > for doing that, but in any case, you will probably want
> to
> > > > > > > > > > expose the version (or range of versions) to use as a
> user
> > > > > > editable setting.
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: Proposal: remove platform versions from platfroms.js

Posted by Michal Mocny <mm...@chromium.org>.
OOOOhhh, Brain you meant cordova-cli's package.json, not the project
workspaces!  I like that.  I like that you can create a project while
offline that way.  I'm also with David/Brian/Others that CLI can have a
default pinned version set, yet we still get cordova platform version
independance.

I thought we were proposing creating a package.json as part of "cordova
create" alongside config.xml, which I was really O_o about.  (I think this
is a likely direction we may end up, but not just nilly willy).

Glad we are coming to agreement, but now we wont have anything to discuss
Friday ;)

-Michal


On Thu, Jul 24, 2014 at 2:56 PM, Brian LeRoux <b...@brian.io> wrote:

> totally agree. the cli package.json can capture which versions of the
> platforms it needs. the platforms can release with reckless abandon
>
> (maybe we'll even hit THREE times this year! ;)
>
>
> On Thu, Jul 24, 2014 at 11:17 AM, David Kemp <dr...@chromium.org> wrote:
>
> > It seems to me that:
> > 1) to make our users happy and get them to consider using newer versions,
> > we need to have the perception of stability. Nice clean, well tested,
> > co-ordinated releases are a good way to get that. For that reason, I
> think
> > a method of providing a 'pinned' release set for the end user is a good
> way
> > to deliver that.
> > 2) to make it easy and fast for the various platform contributors to
> > release new stuff, we need independent platform versioning. That would
> > allow platforms to move ahead separately - as long as all tooling is
> > backward compatible.
> >
> > We should be able to do both.
> >
> >
> >
> > On Thu, Jul 24, 2014 at 1:38 PM, Brian LeRoux <b...@brian.io> wrote:
> >
> > > I am against this change. I am in favor of adding platforms via
> > > package.json, however.
> > >
> > > We need to version lock our dependencies in the CLI. Testing and bug
> > > resolution will be impossible otherwise. (We did this for that reason.)
> > > However, the Platforms don't need to be synchronized. Platforms can
> > release
> > > as they want and the CLI can pick them up as needs be BUT the
> versioning
> > of
> > > dependencies needs to be explicit.
> > >
> > > The only way 'always grab latest' works is when master is pristine and
> > all
> > > development happens on topic branches only to be merged in when
> > everything
> > > works. That is not a capability we currently have.
> > >
> > > "This makes it impossible to release new versions of platforms that
> would
> > > be
> > > usable with the same version of CLI." <--- this is a feature, not a
> bug!
> > > When we want to bump the platforms we *should* have to bump the CLI as
> it
> > > is a dependency.
> > >
> > >
> > >
> > > On Thu, Jul 24, 2014 at 9:19 AM, Andrew Grieve <ag...@chromium.org>
> > > wrote:
> > >
> > > > On Thu, Jul 24, 2014 at 10:40 AM, Chuck Lantz <cl...@microsoft.com>
> > > > wrote:
> > > >
> > > > > To me it sounds like we're talking about something bigger than
> > pinning:
> > > > > What does a Cordova version actually mean?
> > > > >
> > > > > When new macro-level "Cordova" features like splash screens and
> icons
> > > > > support or perhaps coming up with a way to manage code signing and
> > > > > packaging without going into native projects are released, we'll
> need
> > > to
> > > > be
> > > > > able to coordinate a release across a number of different
> platforms.
> > >  So,
> > > > > the way I've always thought about this from and end user
> perspective
> > > is:
> > > >
> > > >
> > > > Certainly having platforms at different versions will be a change
> from
> > > what
> > > > we've had historically. Still, I think it will be for the better.
> > > >
> > > >
> > > > >
> > > > > -Updating the first digit is done for major Cordova level features
> > that
> > > > > affect everyone - and force everyone to change
> > > > >
> > > > But what if only one platform has a change that requires action? Do
> we
> > > not
> > > > bump the major then?, Or do we bump the major and users of other
> > > platforms
> > > > discover it doesn't actually affect them.
> > > >
> > > >
> > > > > -Updating the second digit is about incremental improvements that
> > still
> > > > > constitute new Cordova level features but may only support certain
> > > > platforms
> > > >
> > > > -Updating the last digit ties to bug fixes, perf improvements, and
> > other
> > > > > things that do not have a direct effect on end users
> > > >
> > > >
> > > > > Two questions:
> > > > > -How will documentation work if platforms go to versions
> independent
> > of
> > > > > one another?  For example, consider this:
> > > > >
> > > > >         Android goes to Cordova 3.7.0 one week
> > > > >         iOS goes to Cordova 3.7.0 two weeks later
> > > >
> > > >
> > > > > Does the documentation for the same version update?
> > > > >
> > > >
> > > > I think the easiest way is to just not version the docs. Just have
> them
> > > > always be up-to-date for all released platforms.
> > > >
> > > >
> > > >
> > > > >
> > > > > -Are we saying that there will never be shared infrastructure
> across
> > > > > platforms that the CLI needs?  Otherwise you could get in a
> situation
> > > > where
> > > > > the CLI revs and only one or two platforms are actually supported.
> > >  Given
> > > > > Cordova really is about cross-platform/multi-device development, is
> > > that
> > > > a
> > > > > message we want to send to end users?  What about plugins?
> > > > >
> > > >
> > > > The latest version of CLI must always support all plugins (even old
> > > ones),
> > > > and all platform versions (even old ones). This (I believe), is
> already
> > > the
> > > > case today, and is not too hard to maintain.
> > > >
> > > >
> > > >
> > > > >
> > > > > I also think this commits the community to testing the CLI across a
> > > > number
> > > > > of different versions over time. The CLI would need to be validated
> > > > across
> > > > > a number of different major and minor versions which increases the
> > test
> > > > > burden.
> > > > >
> > > >
> > > > I believe this to already be the case. The current workflow is:
> > > >
> > > > 1. Install a platform (say, android 3.2)
> > > > 2. Update CLI to 3.5.0
> > > > 3. CLI now expected to work with version of platform you have
> > installed.
> > > > 4. Decide you want to update your platform via "cordova platform
> update
> > > > android"
> > > > 5. Now, your project is at android 3.5.0
> > > >
> > > >
> > > >
> > > > >
> > > > > I would argue that plugins are a potential problem right now - the
> > > moment
> > > > > a core plugin drops support for a Cordova version that people are
> > using
> > > > > widely, I think we'll hear about it.  However, in the case of a
> > plugin,
> > > > it
> > > > > is inherently multi-platform and its documentation and
> functionality
> > > > across
> > > > > all platforms will update with one version change.  I think that is
> > the
> > > > > issue with platforms - There needs to be a mechanism to communicate
> > > that
> > > > > something has changed across multiple platforms.
> > > > >
> > > >
> > > > I think your plugin example is a great motivation for having things
> > > > versioned separately. If a plugin drops support for android-3.0.0,
> then
> > > > users are free to stick with an older version of the plugin that does
> > > > support it. I do conceded that our tooling is currently not great
> about
> > > > making this easy to do though.
> > > >
> > > > Plugin features almost always get added one platform at a time.
> > Likewise
> > > > with platform features. I don't think we should be striving to add
> > > features
> > > > across all platforms at a time, because not all platforms even have
> > > people
> > > > actively working on them. What's the gain in trying to synchronize
> > them?
> > > It
> > > > would only cause things to be released more slowly.
> > > >
> > > > For example, we recently had icons and splashscreen support added to
> > CLI
> > > > for some but not all platforms. This actually required no changes in
> > > > platforms, because platforms already supported both. This is a great
> > > > example of why we'd want CLI to not be pinned to platform versions.
> > > Someone
> > > > running cordova-android@3.1.0 would get icon support if they updated
> > > their
> > > > version of CLI, and they wouldn't need to update their platform.
> > > >
> > > >
> > > >
> > > > >
> > > > > On the Android 4.0 churn vs fixes - this sounds more like a
> branching
> > > > > problem that we should not pass on to end users.
> > > > >
> > > > > -Chuck
> > > > >
> > > > > -----Original Message-----
> > > > > From: agrieve@google.com [mailto:agrieve@google.com] On Behalf Of
> > > Andrew
> > > > > Grieve
> > > > > Sent: Thursday, July 24, 2014 6:47 AM
> > > > > To: dev
> > > > > Subject: Re: Proposal: remove platform versions from platfroms.js
> > > > >
> > > > > I agree that the feature will make installing platforms less
> > > > predictable...
> > > > > or at least, just as unpredictable as plugins.
> > > > >
> > > > > It is a good idea to look at exactly what the benefits are though.
> > > > >
> > > > > First - the benefits of removing the idea of a "cadence version":
> > > > > - Android 4.0 is on the horizon, maybe iOS 4.0 as well. Does this
> > mean
> > > > > that when they are ready, we should force all platforms to jump to
> > 4.0?
> > > > > Wouldn't be too bad...
> > > > > - But once at 4.0, what if Windows or Blackberry requires a major
> > > release
> > > > > a couple months later, move all platforms to 5.0?
> > > > > - What if Android undergoes a lot of churn come 4.0, and wants to
> do
> > 3
> > > > > more bugfix releases within the first month after? Do we force all
> > > > > platform's versions to be updated? If not, what does the cadence
> > number
> > > > on
> > > > > CLI look like?
> > > > > - Cadence versioning forces us to try and release multiple
> platforms
> > at
> > > > > the same time.
> > > > >   - E.g. Jesse wants to release windows, but has been waiting for
> > > Android
> > > > > to be ready.
> > > > >   - If each platform just released when it was ready, and had
> > separate
> > > > > blog posts, I think we'd have a happier release process, and would
> > > > release
> > > > > more often.
> > > > >
> > > > > Now, we could do away with cadence version and still have CLI use
> the
> > > > > version in its platforms.js file for each platform. So what does
> this
> > > > > specific change of removing the pinning buy us?
> > > > > - It will lighten the load of doing platform releases.
> > > > > - It will make platforms and plugins both work in the same way.
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On Wed, Jul 23, 2014 at 2:49 PM, Jesse <pu...@gmail.com>
> > > wrote:
> > > > >
> > > > > > I agree, there are many cases where this will lead to complete
> > > > > > un-predictability, and it is still unclear who this 'feature'
> > > benefits.
> > > > > >
> > > > > > How can we guarantee that latest version of a newly added
> platform
> > > > > > supports all the same plugins of the previously added platforms?
> > > > > >
> > > > > > I think ultimately the only benefit is to give us some
> flexibility
> > > > > > with release schedules, but I would much rather have us focus on
> > just
> > > > > > releasing everything more often.  Historically we have never been
> > > able
> > > > > > to deliver a patched point release in under a month, so assuming
> we
> > > > > > can get back to releasing every month, all would be fine, and the
> > > > > > train could just keep rolling forwards. Predictably!
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > @purplecabbage
> > > > > > risingj.com
> > > > > >
> > > > > >
> > > > > > On Wed, Jul 23, 2014 at 10:59 AM, Parashuram Narasimhan (MS OPEN
> > > TECH)
> > > > > > < panarasi@microsoft.com> wrote:
> > > > > >
> > > > > > > I was thinking platforms are devDependencies and plugins are
> > > > > > > dependencies
> > > > > > > :)
> > > > > > >
> > > > > > > In a way, that’s how the bundling works - plugins are packaged
> > with
> > > > > > > the app, while platforms are only needed during development !!
> > > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: Anis KADRI [mailto:anis.kadri@gmail.com]
> > > > > > > Sent: Wednesday, July 23, 2014 10:54 AM
> > > > > > > To: dev@cordova.apache.org
> > > > > > > Subject: Re: Proposal: remove platform versions from
> platfroms.js
> > > > > > >
> > > > > > > +1 for package.json for platforms. plugins might a bit trickier
> > but
> > > > > > > +still
> > > > > > > doable, we could get rid of plugins/ but we somehow need to
> keep
> > > > > > > track of them in node_modules/ (maybe use one of the 10 config
> > > files
> > > > > we have).
> > > > > > > Platforms in package.json should cause no problems though,
> > > > > > > add/remove platforms, pin/unpin versions if required.
> > > > > > >
> > > > > > >
> > > > > > > On Wed, Jul 23, 2014 at 7:36 AM, Michal Mocny <
> > mmocny@chromium.org
> > > >
> > > > > > wrote:
> > > > > > >
> > > > > > > > This sounds like a great topic for hangout Friday.  Glad to
> > have
> > > a
> > > > > > > > concrete proposal / some counter arguments to discuss.
> > > > > > > >
> > > > > > > >
> > > > > > > > On Wed, Jul 23, 2014 at 10:22 AM, Mark Koudritsky
> > > > > > > > <ka...@google.com>
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Currently WebWorks ships specific versions of things.
> > > > > > > > > > If we had shipped unpinned versions of stuff, then
> > eventually
> > > > > > > > > > we would have created projects which our UI wouldn't have
> > > > > > > > > > recognized as valid (because, they e.g. Didn't have a
> > > > > > > > > > ".cordova", or a "hooks", or a
> > > > > > > > "merges"
> > > > > > > > > > or whichever things we had been using to determine if a
> > > > > > > > > > project was
> > > > > > > > > valid).
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > > As long as you continue to ship a version of
> > cordova-backberry
> > > > > > > > > bundled
> > > > > > > > with
> > > > > > > > > WebWorks, it won't be affected by the change I propose. CLI
> > > will
> > > > > > > > > use that bundled version just like it does now using the
> > > > > > > > > settings in .cordova/config.json. We do the same thing with
> > > cca.
> > > > > > > > >
> > > > > > > > > If in the future you decide to stop bundling
> > cordova-blackberry
> > > > > > > > > with WebWorks and switch to the npm published versions, I
> see
> > > > > > > > > several good
> > > > > > > > ways
> > > > > > > > > for doing that, but in any case, you will probably want to
> > > > > > > > > expose the version (or range of versions) to use as a user
> > > > > editable setting.
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: Proposal: remove platform versions from platfroms.js

Posted by Brian LeRoux <b...@brian.io>.
totally agree. the cli package.json can capture which versions of the
platforms it needs. the platforms can release with reckless abandon

(maybe we'll even hit THREE times this year! ;)


On Thu, Jul 24, 2014 at 11:17 AM, David Kemp <dr...@chromium.org> wrote:

> It seems to me that:
> 1) to make our users happy and get them to consider using newer versions,
> we need to have the perception of stability. Nice clean, well tested,
> co-ordinated releases are a good way to get that. For that reason, I think
> a method of providing a 'pinned' release set for the end user is a good way
> to deliver that.
> 2) to make it easy and fast for the various platform contributors to
> release new stuff, we need independent platform versioning. That would
> allow platforms to move ahead separately - as long as all tooling is
> backward compatible.
>
> We should be able to do both.
>
>
>
> On Thu, Jul 24, 2014 at 1:38 PM, Brian LeRoux <b...@brian.io> wrote:
>
> > I am against this change. I am in favor of adding platforms via
> > package.json, however.
> >
> > We need to version lock our dependencies in the CLI. Testing and bug
> > resolution will be impossible otherwise. (We did this for that reason.)
> > However, the Platforms don't need to be synchronized. Platforms can
> release
> > as they want and the CLI can pick them up as needs be BUT the versioning
> of
> > dependencies needs to be explicit.
> >
> > The only way 'always grab latest' works is when master is pristine and
> all
> > development happens on topic branches only to be merged in when
> everything
> > works. That is not a capability we currently have.
> >
> > "This makes it impossible to release new versions of platforms that would
> > be
> > usable with the same version of CLI." <--- this is a feature, not a bug!
> > When we want to bump the platforms we *should* have to bump the CLI as it
> > is a dependency.
> >
> >
> >
> > On Thu, Jul 24, 2014 at 9:19 AM, Andrew Grieve <ag...@chromium.org>
> > wrote:
> >
> > > On Thu, Jul 24, 2014 at 10:40 AM, Chuck Lantz <cl...@microsoft.com>
> > > wrote:
> > >
> > > > To me it sounds like we're talking about something bigger than
> pinning:
> > > > What does a Cordova version actually mean?
> > > >
> > > > When new macro-level "Cordova" features like splash screens and icons
> > > > support or perhaps coming up with a way to manage code signing and
> > > > packaging without going into native projects are released, we'll need
> > to
> > > be
> > > > able to coordinate a release across a number of different platforms.
> >  So,
> > > > the way I've always thought about this from and end user perspective
> > is:
> > >
> > >
> > > Certainly having platforms at different versions will be a change from
> > what
> > > we've had historically. Still, I think it will be for the better.
> > >
> > >
> > > >
> > > > -Updating the first digit is done for major Cordova level features
> that
> > > > affect everyone - and force everyone to change
> > > >
> > > But what if only one platform has a change that requires action? Do we
> > not
> > > bump the major then?, Or do we bump the major and users of other
> > platforms
> > > discover it doesn't actually affect them.
> > >
> > >
> > > > -Updating the second digit is about incremental improvements that
> still
> > > > constitute new Cordova level features but may only support certain
> > > platforms
> > >
> > > -Updating the last digit ties to bug fixes, perf improvements, and
> other
> > > > things that do not have a direct effect on end users
> > >
> > >
> > > > Two questions:
> > > > -How will documentation work if platforms go to versions independent
> of
> > > > one another?  For example, consider this:
> > > >
> > > >         Android goes to Cordova 3.7.0 one week
> > > >         iOS goes to Cordova 3.7.0 two weeks later
> > >
> > >
> > > > Does the documentation for the same version update?
> > > >
> > >
> > > I think the easiest way is to just not version the docs. Just have them
> > > always be up-to-date for all released platforms.
> > >
> > >
> > >
> > > >
> > > > -Are we saying that there will never be shared infrastructure across
> > > > platforms that the CLI needs?  Otherwise you could get in a situation
> > > where
> > > > the CLI revs and only one or two platforms are actually supported.
> >  Given
> > > > Cordova really is about cross-platform/multi-device development, is
> > that
> > > a
> > > > message we want to send to end users?  What about plugins?
> > > >
> > >
> > > The latest version of CLI must always support all plugins (even old
> > ones),
> > > and all platform versions (even old ones). This (I believe), is already
> > the
> > > case today, and is not too hard to maintain.
> > >
> > >
> > >
> > > >
> > > > I also think this commits the community to testing the CLI across a
> > > number
> > > > of different versions over time. The CLI would need to be validated
> > > across
> > > > a number of different major and minor versions which increases the
> test
> > > > burden.
> > > >
> > >
> > > I believe this to already be the case. The current workflow is:
> > >
> > > 1. Install a platform (say, android 3.2)
> > > 2. Update CLI to 3.5.0
> > > 3. CLI now expected to work with version of platform you have
> installed.
> > > 4. Decide you want to update your platform via "cordova platform update
> > > android"
> > > 5. Now, your project is at android 3.5.0
> > >
> > >
> > >
> > > >
> > > > I would argue that plugins are a potential problem right now - the
> > moment
> > > > a core plugin drops support for a Cordova version that people are
> using
> > > > widely, I think we'll hear about it.  However, in the case of a
> plugin,
> > > it
> > > > is inherently multi-platform and its documentation and functionality
> > > across
> > > > all platforms will update with one version change.  I think that is
> the
> > > > issue with platforms - There needs to be a mechanism to communicate
> > that
> > > > something has changed across multiple platforms.
> > > >
> > >
> > > I think your plugin example is a great motivation for having things
> > > versioned separately. If a plugin drops support for android-3.0.0, then
> > > users are free to stick with an older version of the plugin that does
> > > support it. I do conceded that our tooling is currently not great about
> > > making this easy to do though.
> > >
> > > Plugin features almost always get added one platform at a time.
> Likewise
> > > with platform features. I don't think we should be striving to add
> > features
> > > across all platforms at a time, because not all platforms even have
> > people
> > > actively working on them. What's the gain in trying to synchronize
> them?
> > It
> > > would only cause things to be released more slowly.
> > >
> > > For example, we recently had icons and splashscreen support added to
> CLI
> > > for some but not all platforms. This actually required no changes in
> > > platforms, because platforms already supported both. This is a great
> > > example of why we'd want CLI to not be pinned to platform versions.
> > Someone
> > > running cordova-android@3.1.0 would get icon support if they updated
> > their
> > > version of CLI, and they wouldn't need to update their platform.
> > >
> > >
> > >
> > > >
> > > > On the Android 4.0 churn vs fixes - this sounds more like a branching
> > > > problem that we should not pass on to end users.
> > > >
> > > > -Chuck
> > > >
> > > > -----Original Message-----
> > > > From: agrieve@google.com [mailto:agrieve@google.com] On Behalf Of
> > Andrew
> > > > Grieve
> > > > Sent: Thursday, July 24, 2014 6:47 AM
> > > > To: dev
> > > > Subject: Re: Proposal: remove platform versions from platfroms.js
> > > >
> > > > I agree that the feature will make installing platforms less
> > > predictable...
> > > > or at least, just as unpredictable as plugins.
> > > >
> > > > It is a good idea to look at exactly what the benefits are though.
> > > >
> > > > First - the benefits of removing the idea of a "cadence version":
> > > > - Android 4.0 is on the horizon, maybe iOS 4.0 as well. Does this
> mean
> > > > that when they are ready, we should force all platforms to jump to
> 4.0?
> > > > Wouldn't be too bad...
> > > > - But once at 4.0, what if Windows or Blackberry requires a major
> > release
> > > > a couple months later, move all platforms to 5.0?
> > > > - What if Android undergoes a lot of churn come 4.0, and wants to do
> 3
> > > > more bugfix releases within the first month after? Do we force all
> > > > platform's versions to be updated? If not, what does the cadence
> number
> > > on
> > > > CLI look like?
> > > > - Cadence versioning forces us to try and release multiple platforms
> at
> > > > the same time.
> > > >   - E.g. Jesse wants to release windows, but has been waiting for
> > Android
> > > > to be ready.
> > > >   - If each platform just released when it was ready, and had
> separate
> > > > blog posts, I think we'd have a happier release process, and would
> > > release
> > > > more often.
> > > >
> > > > Now, we could do away with cadence version and still have CLI use the
> > > > version in its platforms.js file for each platform. So what does this
> > > > specific change of removing the pinning buy us?
> > > > - It will lighten the load of doing platform releases.
> > > > - It will make platforms and plugins both work in the same way.
> > > >
> > > >
> > > >
> > > >
> > > > On Wed, Jul 23, 2014 at 2:49 PM, Jesse <pu...@gmail.com>
> > wrote:
> > > >
> > > > > I agree, there are many cases where this will lead to complete
> > > > > un-predictability, and it is still unclear who this 'feature'
> > benefits.
> > > > >
> > > > > How can we guarantee that latest version of a newly added platform
> > > > > supports all the same plugins of the previously added platforms?
> > > > >
> > > > > I think ultimately the only benefit is to give us some flexibility
> > > > > with release schedules, but I would much rather have us focus on
> just
> > > > > releasing everything more often.  Historically we have never been
> > able
> > > > > to deliver a patched point release in under a month, so assuming we
> > > > > can get back to releasing every month, all would be fine, and the
> > > > > train could just keep rolling forwards. Predictably!
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > @purplecabbage
> > > > > risingj.com
> > > > >
> > > > >
> > > > > On Wed, Jul 23, 2014 at 10:59 AM, Parashuram Narasimhan (MS OPEN
> > TECH)
> > > > > < panarasi@microsoft.com> wrote:
> > > > >
> > > > > > I was thinking platforms are devDependencies and plugins are
> > > > > > dependencies
> > > > > > :)
> > > > > >
> > > > > > In a way, that’s how the bundling works - plugins are packaged
> with
> > > > > > the app, while platforms are only needed during development !!
> > > > > >
> > > > > > -----Original Message-----
> > > > > > From: Anis KADRI [mailto:anis.kadri@gmail.com]
> > > > > > Sent: Wednesday, July 23, 2014 10:54 AM
> > > > > > To: dev@cordova.apache.org
> > > > > > Subject: Re: Proposal: remove platform versions from platfroms.js
> > > > > >
> > > > > > +1 for package.json for platforms. plugins might a bit trickier
> but
> > > > > > +still
> > > > > > doable, we could get rid of plugins/ but we somehow need to keep
> > > > > > track of them in node_modules/ (maybe use one of the 10 config
> > files
> > > > we have).
> > > > > > Platforms in package.json should cause no problems though,
> > > > > > add/remove platforms, pin/unpin versions if required.
> > > > > >
> > > > > >
> > > > > > On Wed, Jul 23, 2014 at 7:36 AM, Michal Mocny <
> mmocny@chromium.org
> > >
> > > > > wrote:
> > > > > >
> > > > > > > This sounds like a great topic for hangout Friday.  Glad to
> have
> > a
> > > > > > > concrete proposal / some counter arguments to discuss.
> > > > > > >
> > > > > > >
> > > > > > > On Wed, Jul 23, 2014 at 10:22 AM, Mark Koudritsky
> > > > > > > <ka...@google.com>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > >
> > > > > > > > > Currently WebWorks ships specific versions of things.
> > > > > > > > > If we had shipped unpinned versions of stuff, then
> eventually
> > > > > > > > > we would have created projects which our UI wouldn't have
> > > > > > > > > recognized as valid (because, they e.g. Didn't have a
> > > > > > > > > ".cordova", or a "hooks", or a
> > > > > > > "merges"
> > > > > > > > > or whichever things we had been using to determine if a
> > > > > > > > > project was
> > > > > > > > valid).
> > > > > > > > >
> > > > > > > >
> > > > > > > > As long as you continue to ship a version of
> cordova-backberry
> > > > > > > > bundled
> > > > > > > with
> > > > > > > > WebWorks, it won't be affected by the change I propose. CLI
> > will
> > > > > > > > use that bundled version just like it does now using the
> > > > > > > > settings in .cordova/config.json. We do the same thing with
> > cca.
> > > > > > > >
> > > > > > > > If in the future you decide to stop bundling
> cordova-blackberry
> > > > > > > > with WebWorks and switch to the npm published versions, I see
> > > > > > > > several good
> > > > > > > ways
> > > > > > > > for doing that, but in any case, you will probably want to
> > > > > > > > expose the version (or range of versions) to use as a user
> > > > editable setting.
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: Proposal: remove platform versions from platfroms.js

Posted by David Kemp <dr...@chromium.org>.
It seems to me that:
1) to make our users happy and get them to consider using newer versions,
we need to have the perception of stability. Nice clean, well tested,
co-ordinated releases are a good way to get that. For that reason, I think
a method of providing a 'pinned' release set for the end user is a good way
to deliver that.
2) to make it easy and fast for the various platform contributors to
release new stuff, we need independent platform versioning. That would
allow platforms to move ahead separately - as long as all tooling is
backward compatible.

We should be able to do both.



On Thu, Jul 24, 2014 at 1:38 PM, Brian LeRoux <b...@brian.io> wrote:

> I am against this change. I am in favor of adding platforms via
> package.json, however.
>
> We need to version lock our dependencies in the CLI. Testing and bug
> resolution will be impossible otherwise. (We did this for that reason.)
> However, the Platforms don't need to be synchronized. Platforms can release
> as they want and the CLI can pick them up as needs be BUT the versioning of
> dependencies needs to be explicit.
>
> The only way 'always grab latest' works is when master is pristine and all
> development happens on topic branches only to be merged in when everything
> works. That is not a capability we currently have.
>
> "This makes it impossible to release new versions of platforms that would
> be
> usable with the same version of CLI." <--- this is a feature, not a bug!
> When we want to bump the platforms we *should* have to bump the CLI as it
> is a dependency.
>
>
>
> On Thu, Jul 24, 2014 at 9:19 AM, Andrew Grieve <ag...@chromium.org>
> wrote:
>
> > On Thu, Jul 24, 2014 at 10:40 AM, Chuck Lantz <cl...@microsoft.com>
> > wrote:
> >
> > > To me it sounds like we're talking about something bigger than pinning:
> > > What does a Cordova version actually mean?
> > >
> > > When new macro-level "Cordova" features like splash screens and icons
> > > support or perhaps coming up with a way to manage code signing and
> > > packaging without going into native projects are released, we'll need
> to
> > be
> > > able to coordinate a release across a number of different platforms.
>  So,
> > > the way I've always thought about this from and end user perspective
> is:
> >
> >
> > Certainly having platforms at different versions will be a change from
> what
> > we've had historically. Still, I think it will be for the better.
> >
> >
> > >
> > > -Updating the first digit is done for major Cordova level features that
> > > affect everyone - and force everyone to change
> > >
> > But what if only one platform has a change that requires action? Do we
> not
> > bump the major then?, Or do we bump the major and users of other
> platforms
> > discover it doesn't actually affect them.
> >
> >
> > > -Updating the second digit is about incremental improvements that still
> > > constitute new Cordova level features but may only support certain
> > platforms
> >
> > -Updating the last digit ties to bug fixes, perf improvements, and other
> > > things that do not have a direct effect on end users
> >
> >
> > > Two questions:
> > > -How will documentation work if platforms go to versions independent of
> > > one another?  For example, consider this:
> > >
> > >         Android goes to Cordova 3.7.0 one week
> > >         iOS goes to Cordova 3.7.0 two weeks later
> >
> >
> > > Does the documentation for the same version update?
> > >
> >
> > I think the easiest way is to just not version the docs. Just have them
> > always be up-to-date for all released platforms.
> >
> >
> >
> > >
> > > -Are we saying that there will never be shared infrastructure across
> > > platforms that the CLI needs?  Otherwise you could get in a situation
> > where
> > > the CLI revs and only one or two platforms are actually supported.
>  Given
> > > Cordova really is about cross-platform/multi-device development, is
> that
> > a
> > > message we want to send to end users?  What about plugins?
> > >
> >
> > The latest version of CLI must always support all plugins (even old
> ones),
> > and all platform versions (even old ones). This (I believe), is already
> the
> > case today, and is not too hard to maintain.
> >
> >
> >
> > >
> > > I also think this commits the community to testing the CLI across a
> > number
> > > of different versions over time. The CLI would need to be validated
> > across
> > > a number of different major and minor versions which increases the test
> > > burden.
> > >
> >
> > I believe this to already be the case. The current workflow is:
> >
> > 1. Install a platform (say, android 3.2)
> > 2. Update CLI to 3.5.0
> > 3. CLI now expected to work with version of platform you have installed.
> > 4. Decide you want to update your platform via "cordova platform update
> > android"
> > 5. Now, your project is at android 3.5.0
> >
> >
> >
> > >
> > > I would argue that plugins are a potential problem right now - the
> moment
> > > a core plugin drops support for a Cordova version that people are using
> > > widely, I think we'll hear about it.  However, in the case of a plugin,
> > it
> > > is inherently multi-platform and its documentation and functionality
> > across
> > > all platforms will update with one version change.  I think that is the
> > > issue with platforms - There needs to be a mechanism to communicate
> that
> > > something has changed across multiple platforms.
> > >
> >
> > I think your plugin example is a great motivation for having things
> > versioned separately. If a plugin drops support for android-3.0.0, then
> > users are free to stick with an older version of the plugin that does
> > support it. I do conceded that our tooling is currently not great about
> > making this easy to do though.
> >
> > Plugin features almost always get added one platform at a time. Likewise
> > with platform features. I don't think we should be striving to add
> features
> > across all platforms at a time, because not all platforms even have
> people
> > actively working on them. What's the gain in trying to synchronize them?
> It
> > would only cause things to be released more slowly.
> >
> > For example, we recently had icons and splashscreen support added to CLI
> > for some but not all platforms. This actually required no changes in
> > platforms, because platforms already supported both. This is a great
> > example of why we'd want CLI to not be pinned to platform versions.
> Someone
> > running cordova-android@3.1.0 would get icon support if they updated
> their
> > version of CLI, and they wouldn't need to update their platform.
> >
> >
> >
> > >
> > > On the Android 4.0 churn vs fixes - this sounds more like a branching
> > > problem that we should not pass on to end users.
> > >
> > > -Chuck
> > >
> > > -----Original Message-----
> > > From: agrieve@google.com [mailto:agrieve@google.com] On Behalf Of
> Andrew
> > > Grieve
> > > Sent: Thursday, July 24, 2014 6:47 AM
> > > To: dev
> > > Subject: Re: Proposal: remove platform versions from platfroms.js
> > >
> > > I agree that the feature will make installing platforms less
> > predictable...
> > > or at least, just as unpredictable as plugins.
> > >
> > > It is a good idea to look at exactly what the benefits are though.
> > >
> > > First - the benefits of removing the idea of a "cadence version":
> > > - Android 4.0 is on the horizon, maybe iOS 4.0 as well. Does this mean
> > > that when they are ready, we should force all platforms to jump to 4.0?
> > > Wouldn't be too bad...
> > > - But once at 4.0, what if Windows or Blackberry requires a major
> release
> > > a couple months later, move all platforms to 5.0?
> > > - What if Android undergoes a lot of churn come 4.0, and wants to do 3
> > > more bugfix releases within the first month after? Do we force all
> > > platform's versions to be updated? If not, what does the cadence number
> > on
> > > CLI look like?
> > > - Cadence versioning forces us to try and release multiple platforms at
> > > the same time.
> > >   - E.g. Jesse wants to release windows, but has been waiting for
> Android
> > > to be ready.
> > >   - If each platform just released when it was ready, and had separate
> > > blog posts, I think we'd have a happier release process, and would
> > release
> > > more often.
> > >
> > > Now, we could do away with cadence version and still have CLI use the
> > > version in its platforms.js file for each platform. So what does this
> > > specific change of removing the pinning buy us?
> > > - It will lighten the load of doing platform releases.
> > > - It will make platforms and plugins both work in the same way.
> > >
> > >
> > >
> > >
> > > On Wed, Jul 23, 2014 at 2:49 PM, Jesse <pu...@gmail.com>
> wrote:
> > >
> > > > I agree, there are many cases where this will lead to complete
> > > > un-predictability, and it is still unclear who this 'feature'
> benefits.
> > > >
> > > > How can we guarantee that latest version of a newly added platform
> > > > supports all the same plugins of the previously added platforms?
> > > >
> > > > I think ultimately the only benefit is to give us some flexibility
> > > > with release schedules, but I would much rather have us focus on just
> > > > releasing everything more often.  Historically we have never been
> able
> > > > to deliver a patched point release in under a month, so assuming we
> > > > can get back to releasing every month, all would be fine, and the
> > > > train could just keep rolling forwards. Predictably!
> > > >
> > > >
> > > >
> > > >
> > > > @purplecabbage
> > > > risingj.com
> > > >
> > > >
> > > > On Wed, Jul 23, 2014 at 10:59 AM, Parashuram Narasimhan (MS OPEN
> TECH)
> > > > < panarasi@microsoft.com> wrote:
> > > >
> > > > > I was thinking platforms are devDependencies and plugins are
> > > > > dependencies
> > > > > :)
> > > > >
> > > > > In a way, that’s how the bundling works - plugins are packaged with
> > > > > the app, while platforms are only needed during development !!
> > > > >
> > > > > -----Original Message-----
> > > > > From: Anis KADRI [mailto:anis.kadri@gmail.com]
> > > > > Sent: Wednesday, July 23, 2014 10:54 AM
> > > > > To: dev@cordova.apache.org
> > > > > Subject: Re: Proposal: remove platform versions from platfroms.js
> > > > >
> > > > > +1 for package.json for platforms. plugins might a bit trickier but
> > > > > +still
> > > > > doable, we could get rid of plugins/ but we somehow need to keep
> > > > > track of them in node_modules/ (maybe use one of the 10 config
> files
> > > we have).
> > > > > Platforms in package.json should cause no problems though,
> > > > > add/remove platforms, pin/unpin versions if required.
> > > > >
> > > > >
> > > > > On Wed, Jul 23, 2014 at 7:36 AM, Michal Mocny <mmocny@chromium.org
> >
> > > > wrote:
> > > > >
> > > > > > This sounds like a great topic for hangout Friday.  Glad to have
> a
> > > > > > concrete proposal / some counter arguments to discuss.
> > > > > >
> > > > > >
> > > > > > On Wed, Jul 23, 2014 at 10:22 AM, Mark Koudritsky
> > > > > > <ka...@google.com>
> > > > > > wrote:
> > > > > >
> > > > > > > >
> > > > > > > > Currently WebWorks ships specific versions of things.
> > > > > > > > If we had shipped unpinned versions of stuff, then eventually
> > > > > > > > we would have created projects which our UI wouldn't have
> > > > > > > > recognized as valid (because, they e.g. Didn't have a
> > > > > > > > ".cordova", or a "hooks", or a
> > > > > > "merges"
> > > > > > > > or whichever things we had been using to determine if a
> > > > > > > > project was
> > > > > > > valid).
> > > > > > > >
> > > > > > >
> > > > > > > As long as you continue to ship a version of cordova-backberry
> > > > > > > bundled
> > > > > > with
> > > > > > > WebWorks, it won't be affected by the change I propose. CLI
> will
> > > > > > > use that bundled version just like it does now using the
> > > > > > > settings in .cordova/config.json. We do the same thing with
> cca.
> > > > > > >
> > > > > > > If in the future you decide to stop bundling cordova-blackberry
> > > > > > > with WebWorks and switch to the npm published versions, I see
> > > > > > > several good
> > > > > > ways
> > > > > > > for doing that, but in any case, you will probably want to
> > > > > > > expose the version (or range of versions) to use as a user
> > > editable setting.
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: Proposal: remove platform versions from platfroms.js

Posted by Brian LeRoux <b...@brian.io>.
I am against this change. I am in favor of adding platforms via
package.json, however.

We need to version lock our dependencies in the CLI. Testing and bug
resolution will be impossible otherwise. (We did this for that reason.)
However, the Platforms don't need to be synchronized. Platforms can release
as they want and the CLI can pick them up as needs be BUT the versioning of
dependencies needs to be explicit.

The only way 'always grab latest' works is when master is pristine and all
development happens on topic branches only to be merged in when everything
works. That is not a capability we currently have.

"This makes it impossible to release new versions of platforms that would be
usable with the same version of CLI." <--- this is a feature, not a bug!
When we want to bump the platforms we *should* have to bump the CLI as it
is a dependency.



On Thu, Jul 24, 2014 at 9:19 AM, Andrew Grieve <ag...@chromium.org> wrote:

> On Thu, Jul 24, 2014 at 10:40 AM, Chuck Lantz <cl...@microsoft.com>
> wrote:
>
> > To me it sounds like we're talking about something bigger than pinning:
> > What does a Cordova version actually mean?
> >
> > When new macro-level "Cordova" features like splash screens and icons
> > support or perhaps coming up with a way to manage code signing and
> > packaging without going into native projects are released, we'll need to
> be
> > able to coordinate a release across a number of different platforms.  So,
> > the way I've always thought about this from and end user perspective is:
>
>
> Certainly having platforms at different versions will be a change from what
> we've had historically. Still, I think it will be for the better.
>
>
> >
> > -Updating the first digit is done for major Cordova level features that
> > affect everyone - and force everyone to change
> >
> But what if only one platform has a change that requires action? Do we not
> bump the major then?, Or do we bump the major and users of other platforms
> discover it doesn't actually affect them.
>
>
> > -Updating the second digit is about incremental improvements that still
> > constitute new Cordova level features but may only support certain
> platforms
>
> -Updating the last digit ties to bug fixes, perf improvements, and other
> > things that do not have a direct effect on end users
>
>
> > Two questions:
> > -How will documentation work if platforms go to versions independent of
> > one another?  For example, consider this:
> >
> >         Android goes to Cordova 3.7.0 one week
> >         iOS goes to Cordova 3.7.0 two weeks later
>
>
> > Does the documentation for the same version update?
> >
>
> I think the easiest way is to just not version the docs. Just have them
> always be up-to-date for all released platforms.
>
>
>
> >
> > -Are we saying that there will never be shared infrastructure across
> > platforms that the CLI needs?  Otherwise you could get in a situation
> where
> > the CLI revs and only one or two platforms are actually supported.  Given
> > Cordova really is about cross-platform/multi-device development, is that
> a
> > message we want to send to end users?  What about plugins?
> >
>
> The latest version of CLI must always support all plugins (even old ones),
> and all platform versions (even old ones). This (I believe), is already the
> case today, and is not too hard to maintain.
>
>
>
> >
> > I also think this commits the community to testing the CLI across a
> number
> > of different versions over time. The CLI would need to be validated
> across
> > a number of different major and minor versions which increases the test
> > burden.
> >
>
> I believe this to already be the case. The current workflow is:
>
> 1. Install a platform (say, android 3.2)
> 2. Update CLI to 3.5.0
> 3. CLI now expected to work with version of platform you have installed.
> 4. Decide you want to update your platform via "cordova platform update
> android"
> 5. Now, your project is at android 3.5.0
>
>
>
> >
> > I would argue that plugins are a potential problem right now - the moment
> > a core plugin drops support for a Cordova version that people are using
> > widely, I think we'll hear about it.  However, in the case of a plugin,
> it
> > is inherently multi-platform and its documentation and functionality
> across
> > all platforms will update with one version change.  I think that is the
> > issue with platforms - There needs to be a mechanism to communicate that
> > something has changed across multiple platforms.
> >
>
> I think your plugin example is a great motivation for having things
> versioned separately. If a plugin drops support for android-3.0.0, then
> users are free to stick with an older version of the plugin that does
> support it. I do conceded that our tooling is currently not great about
> making this easy to do though.
>
> Plugin features almost always get added one platform at a time. Likewise
> with platform features. I don't think we should be striving to add features
> across all platforms at a time, because not all platforms even have people
> actively working on them. What's the gain in trying to synchronize them? It
> would only cause things to be released more slowly.
>
> For example, we recently had icons and splashscreen support added to CLI
> for some but not all platforms. This actually required no changes in
> platforms, because platforms already supported both. This is a great
> example of why we'd want CLI to not be pinned to platform versions. Someone
> running cordova-android@3.1.0 would get icon support if they updated their
> version of CLI, and they wouldn't need to update their platform.
>
>
>
> >
> > On the Android 4.0 churn vs fixes - this sounds more like a branching
> > problem that we should not pass on to end users.
> >
> > -Chuck
> >
> > -----Original Message-----
> > From: agrieve@google.com [mailto:agrieve@google.com] On Behalf Of Andrew
> > Grieve
> > Sent: Thursday, July 24, 2014 6:47 AM
> > To: dev
> > Subject: Re: Proposal: remove platform versions from platfroms.js
> >
> > I agree that the feature will make installing platforms less
> predictable...
> > or at least, just as unpredictable as plugins.
> >
> > It is a good idea to look at exactly what the benefits are though.
> >
> > First - the benefits of removing the idea of a "cadence version":
> > - Android 4.0 is on the horizon, maybe iOS 4.0 as well. Does this mean
> > that when they are ready, we should force all platforms to jump to 4.0?
> > Wouldn't be too bad...
> > - But once at 4.0, what if Windows or Blackberry requires a major release
> > a couple months later, move all platforms to 5.0?
> > - What if Android undergoes a lot of churn come 4.0, and wants to do 3
> > more bugfix releases within the first month after? Do we force all
> > platform's versions to be updated? If not, what does the cadence number
> on
> > CLI look like?
> > - Cadence versioning forces us to try and release multiple platforms at
> > the same time.
> >   - E.g. Jesse wants to release windows, but has been waiting for Android
> > to be ready.
> >   - If each platform just released when it was ready, and had separate
> > blog posts, I think we'd have a happier release process, and would
> release
> > more often.
> >
> > Now, we could do away with cadence version and still have CLI use the
> > version in its platforms.js file for each platform. So what does this
> > specific change of removing the pinning buy us?
> > - It will lighten the load of doing platform releases.
> > - It will make platforms and plugins both work in the same way.
> >
> >
> >
> >
> > On Wed, Jul 23, 2014 at 2:49 PM, Jesse <pu...@gmail.com> wrote:
> >
> > > I agree, there are many cases where this will lead to complete
> > > un-predictability, and it is still unclear who this 'feature' benefits.
> > >
> > > How can we guarantee that latest version of a newly added platform
> > > supports all the same plugins of the previously added platforms?
> > >
> > > I think ultimately the only benefit is to give us some flexibility
> > > with release schedules, but I would much rather have us focus on just
> > > releasing everything more often.  Historically we have never been able
> > > to deliver a patched point release in under a month, so assuming we
> > > can get back to releasing every month, all would be fine, and the
> > > train could just keep rolling forwards. Predictably!
> > >
> > >
> > >
> > >
> > > @purplecabbage
> > > risingj.com
> > >
> > >
> > > On Wed, Jul 23, 2014 at 10:59 AM, Parashuram Narasimhan (MS OPEN TECH)
> > > < panarasi@microsoft.com> wrote:
> > >
> > > > I was thinking platforms are devDependencies and plugins are
> > > > dependencies
> > > > :)
> > > >
> > > > In a way, that’s how the bundling works - plugins are packaged with
> > > > the app, while platforms are only needed during development !!
> > > >
> > > > -----Original Message-----
> > > > From: Anis KADRI [mailto:anis.kadri@gmail.com]
> > > > Sent: Wednesday, July 23, 2014 10:54 AM
> > > > To: dev@cordova.apache.org
> > > > Subject: Re: Proposal: remove platform versions from platfroms.js
> > > >
> > > > +1 for package.json for platforms. plugins might a bit trickier but
> > > > +still
> > > > doable, we could get rid of plugins/ but we somehow need to keep
> > > > track of them in node_modules/ (maybe use one of the 10 config files
> > we have).
> > > > Platforms in package.json should cause no problems though,
> > > > add/remove platforms, pin/unpin versions if required.
> > > >
> > > >
> > > > On Wed, Jul 23, 2014 at 7:36 AM, Michal Mocny <mm...@chromium.org>
> > > wrote:
> > > >
> > > > > This sounds like a great topic for hangout Friday.  Glad to have a
> > > > > concrete proposal / some counter arguments to discuss.
> > > > >
> > > > >
> > > > > On Wed, Jul 23, 2014 at 10:22 AM, Mark Koudritsky
> > > > > <ka...@google.com>
> > > > > wrote:
> > > > >
> > > > > > >
> > > > > > > Currently WebWorks ships specific versions of things.
> > > > > > > If we had shipped unpinned versions of stuff, then eventually
> > > > > > > we would have created projects which our UI wouldn't have
> > > > > > > recognized as valid (because, they e.g. Didn't have a
> > > > > > > ".cordova", or a "hooks", or a
> > > > > "merges"
> > > > > > > or whichever things we had been using to determine if a
> > > > > > > project was
> > > > > > valid).
> > > > > > >
> > > > > >
> > > > > > As long as you continue to ship a version of cordova-backberry
> > > > > > bundled
> > > > > with
> > > > > > WebWorks, it won't be affected by the change I propose. CLI will
> > > > > > use that bundled version just like it does now using the
> > > > > > settings in .cordova/config.json. We do the same thing with cca.
> > > > > >
> > > > > > If in the future you decide to stop bundling cordova-blackberry
> > > > > > with WebWorks and switch to the npm published versions, I see
> > > > > > several good
> > > > > ways
> > > > > > for doing that, but in any case, you will probably want to
> > > > > > expose the version (or range of versions) to use as a user
> > editable setting.
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: Proposal: remove platform versions from platfroms.js

Posted by Andrew Grieve <ag...@chromium.org>.
On Thu, Jul 24, 2014 at 10:40 AM, Chuck Lantz <cl...@microsoft.com> wrote:

> To me it sounds like we're talking about something bigger than pinning:
> What does a Cordova version actually mean?
>
> When new macro-level "Cordova" features like splash screens and icons
> support or perhaps coming up with a way to manage code signing and
> packaging without going into native projects are released, we'll need to be
> able to coordinate a release across a number of different platforms.  So,
> the way I've always thought about this from and end user perspective is:


Certainly having platforms at different versions will be a change from what
we've had historically. Still, I think it will be for the better.


>
> -Updating the first digit is done for major Cordova level features that
> affect everyone - and force everyone to change
>
But what if only one platform has a change that requires action? Do we not
bump the major then?, Or do we bump the major and users of other platforms
discover it doesn't actually affect them.


> -Updating the second digit is about incremental improvements that still
> constitute new Cordova level features but may only support certain platforms

-Updating the last digit ties to bug fixes, perf improvements, and other
> things that do not have a direct effect on end users


> Two questions:
> -How will documentation work if platforms go to versions independent of
> one another?  For example, consider this:
>
>         Android goes to Cordova 3.7.0 one week
>         iOS goes to Cordova 3.7.0 two weeks later


> Does the documentation for the same version update?
>

I think the easiest way is to just not version the docs. Just have them
always be up-to-date for all released platforms.



>
> -Are we saying that there will never be shared infrastructure across
> platforms that the CLI needs?  Otherwise you could get in a situation where
> the CLI revs and only one or two platforms are actually supported.  Given
> Cordova really is about cross-platform/multi-device development, is that a
> message we want to send to end users?  What about plugins?
>

The latest version of CLI must always support all plugins (even old ones),
and all platform versions (even old ones). This (I believe), is already the
case today, and is not too hard to maintain.



>
> I also think this commits the community to testing the CLI across a number
> of different versions over time. The CLI would need to be validated across
> a number of different major and minor versions which increases the test
> burden.
>

I believe this to already be the case. The current workflow is:

1. Install a platform (say, android 3.2)
2. Update CLI to 3.5.0
3. CLI now expected to work with version of platform you have installed.
4. Decide you want to update your platform via "cordova platform update
android"
5. Now, your project is at android 3.5.0



>
> I would argue that plugins are a potential problem right now - the moment
> a core plugin drops support for a Cordova version that people are using
> widely, I think we'll hear about it.  However, in the case of a plugin, it
> is inherently multi-platform and its documentation and functionality across
> all platforms will update with one version change.  I think that is the
> issue with platforms - There needs to be a mechanism to communicate that
> something has changed across multiple platforms.
>

I think your plugin example is a great motivation for having things
versioned separately. If a plugin drops support for android-3.0.0, then
users are free to stick with an older version of the plugin that does
support it. I do conceded that our tooling is currently not great about
making this easy to do though.

Plugin features almost always get added one platform at a time. Likewise
with platform features. I don't think we should be striving to add features
across all platforms at a time, because not all platforms even have people
actively working on them. What's the gain in trying to synchronize them? It
would only cause things to be released more slowly.

For example, we recently had icons and splashscreen support added to CLI
for some but not all platforms. This actually required no changes in
platforms, because platforms already supported both. This is a great
example of why we'd want CLI to not be pinned to platform versions. Someone
running cordova-android@3.1.0 would get icon support if they updated their
version of CLI, and they wouldn't need to update their platform.



>
> On the Android 4.0 churn vs fixes - this sounds more like a branching
> problem that we should not pass on to end users.
>
> -Chuck
>
> -----Original Message-----
> From: agrieve@google.com [mailto:agrieve@google.com] On Behalf Of Andrew
> Grieve
> Sent: Thursday, July 24, 2014 6:47 AM
> To: dev
> Subject: Re: Proposal: remove platform versions from platfroms.js
>
> I agree that the feature will make installing platforms less predictable...
> or at least, just as unpredictable as plugins.
>
> It is a good idea to look at exactly what the benefits are though.
>
> First - the benefits of removing the idea of a "cadence version":
> - Android 4.0 is on the horizon, maybe iOS 4.0 as well. Does this mean
> that when they are ready, we should force all platforms to jump to 4.0?
> Wouldn't be too bad...
> - But once at 4.0, what if Windows or Blackberry requires a major release
> a couple months later, move all platforms to 5.0?
> - What if Android undergoes a lot of churn come 4.0, and wants to do 3
> more bugfix releases within the first month after? Do we force all
> platform's versions to be updated? If not, what does the cadence number on
> CLI look like?
> - Cadence versioning forces us to try and release multiple platforms at
> the same time.
>   - E.g. Jesse wants to release windows, but has been waiting for Android
> to be ready.
>   - If each platform just released when it was ready, and had separate
> blog posts, I think we'd have a happier release process, and would release
> more often.
>
> Now, we could do away with cadence version and still have CLI use the
> version in its platforms.js file for each platform. So what does this
> specific change of removing the pinning buy us?
> - It will lighten the load of doing platform releases.
> - It will make platforms and plugins both work in the same way.
>
>
>
>
> On Wed, Jul 23, 2014 at 2:49 PM, Jesse <pu...@gmail.com> wrote:
>
> > I agree, there are many cases where this will lead to complete
> > un-predictability, and it is still unclear who this 'feature' benefits.
> >
> > How can we guarantee that latest version of a newly added platform
> > supports all the same plugins of the previously added platforms?
> >
> > I think ultimately the only benefit is to give us some flexibility
> > with release schedules, but I would much rather have us focus on just
> > releasing everything more often.  Historically we have never been able
> > to deliver a patched point release in under a month, so assuming we
> > can get back to releasing every month, all would be fine, and the
> > train could just keep rolling forwards. Predictably!
> >
> >
> >
> >
> > @purplecabbage
> > risingj.com
> >
> >
> > On Wed, Jul 23, 2014 at 10:59 AM, Parashuram Narasimhan (MS OPEN TECH)
> > < panarasi@microsoft.com> wrote:
> >
> > > I was thinking platforms are devDependencies and plugins are
> > > dependencies
> > > :)
> > >
> > > In a way, that’s how the bundling works - plugins are packaged with
> > > the app, while platforms are only needed during development !!
> > >
> > > -----Original Message-----
> > > From: Anis KADRI [mailto:anis.kadri@gmail.com]
> > > Sent: Wednesday, July 23, 2014 10:54 AM
> > > To: dev@cordova.apache.org
> > > Subject: Re: Proposal: remove platform versions from platfroms.js
> > >
> > > +1 for package.json for platforms. plugins might a bit trickier but
> > > +still
> > > doable, we could get rid of plugins/ but we somehow need to keep
> > > track of them in node_modules/ (maybe use one of the 10 config files
> we have).
> > > Platforms in package.json should cause no problems though,
> > > add/remove platforms, pin/unpin versions if required.
> > >
> > >
> > > On Wed, Jul 23, 2014 at 7:36 AM, Michal Mocny <mm...@chromium.org>
> > wrote:
> > >
> > > > This sounds like a great topic for hangout Friday.  Glad to have a
> > > > concrete proposal / some counter arguments to discuss.
> > > >
> > > >
> > > > On Wed, Jul 23, 2014 at 10:22 AM, Mark Koudritsky
> > > > <ka...@google.com>
> > > > wrote:
> > > >
> > > > > >
> > > > > > Currently WebWorks ships specific versions of things.
> > > > > > If we had shipped unpinned versions of stuff, then eventually
> > > > > > we would have created projects which our UI wouldn't have
> > > > > > recognized as valid (because, they e.g. Didn't have a
> > > > > > ".cordova", or a "hooks", or a
> > > > "merges"
> > > > > > or whichever things we had been using to determine if a
> > > > > > project was
> > > > > valid).
> > > > > >
> > > > >
> > > > > As long as you continue to ship a version of cordova-backberry
> > > > > bundled
> > > > with
> > > > > WebWorks, it won't be affected by the change I propose. CLI will
> > > > > use that bundled version just like it does now using the
> > > > > settings in .cordova/config.json. We do the same thing with cca.
> > > > >
> > > > > If in the future you decide to stop bundling cordova-blackberry
> > > > > with WebWorks and switch to the npm published versions, I see
> > > > > several good
> > > > ways
> > > > > for doing that, but in any case, you will probably want to
> > > > > expose the version (or range of versions) to use as a user
> editable setting.
> > > > >
> > > >
> > >
> >
>

RE: Proposal: remove platform versions from platfroms.js

Posted by Chuck Lantz <cl...@microsoft.com>.
To me it sounds like we're talking about something bigger than pinning: What does a Cordova version actually mean?

When new macro-level "Cordova" features like splash screens and icons support or perhaps coming up with a way to manage code signing and packaging without going into native projects are released, we'll need to be able to coordinate a release across a number of different platforms.  So, the way I've always thought about this from and end user perspective is:

-Updating the first digit is done for major Cordova level features that affect everyone - and force everyone to change
-Updating the second digit is about incremental improvements that still constitute new Cordova level features but may only support certain platforms
-Updating the last digit ties to bug fixes, perf improvements, and other things that do not have a direct effect on end users 

Two questions:
-How will documentation work if platforms go to versions independent of one another?  For example, consider this:

	Android goes to Cordova 3.7.0 one week
	iOS goes to Cordova 3.7.0 two weeks later

Does the documentation for the same version update?  

-Are we saying that there will never be shared infrastructure across platforms that the CLI needs?  Otherwise you could get in a situation where the CLI revs and only one or two platforms are actually supported.  Given Cordova really is about cross-platform/multi-device development, is that a message we want to send to end users?  What about plugins?

I also think this commits the community to testing the CLI across a number of different versions over time. The CLI would need to be validated across a number of different major and minor versions which increases the test burden.

I would argue that plugins are a potential problem right now - the moment a core plugin drops support for a Cordova version that people are using widely, I think we'll hear about it.  However, in the case of a plugin, it is inherently multi-platform and its documentation and functionality across all platforms will update with one version change.  I think that is the issue with platforms - There needs to be a mechanism to communicate that something has changed across multiple platforms.  

On the Android 4.0 churn vs fixes - this sounds more like a branching problem that we should not pass on to end users.  

-Chuck

-----Original Message-----
From: agrieve@google.com [mailto:agrieve@google.com] On Behalf Of Andrew Grieve
Sent: Thursday, July 24, 2014 6:47 AM
To: dev
Subject: Re: Proposal: remove platform versions from platfroms.js

I agree that the feature will make installing platforms less predictable...
or at least, just as unpredictable as plugins.

It is a good idea to look at exactly what the benefits are though.

First - the benefits of removing the idea of a "cadence version":
- Android 4.0 is on the horizon, maybe iOS 4.0 as well. Does this mean that when they are ready, we should force all platforms to jump to 4.0? Wouldn't be too bad...
- But once at 4.0, what if Windows or Blackberry requires a major release a couple months later, move all platforms to 5.0?
- What if Android undergoes a lot of churn come 4.0, and wants to do 3 more bugfix releases within the first month after? Do we force all platform's versions to be updated? If not, what does the cadence number on CLI look like?
- Cadence versioning forces us to try and release multiple platforms at the same time.
  - E.g. Jesse wants to release windows, but has been waiting for Android to be ready.
  - If each platform just released when it was ready, and had separate blog posts, I think we'd have a happier release process, and would release more often.

Now, we could do away with cadence version and still have CLI use the version in its platforms.js file for each platform. So what does this specific change of removing the pinning buy us?
- It will lighten the load of doing platform releases.
- It will make platforms and plugins both work in the same way.




On Wed, Jul 23, 2014 at 2:49 PM, Jesse <pu...@gmail.com> wrote:

> I agree, there are many cases where this will lead to complete 
> un-predictability, and it is still unclear who this 'feature' benefits.
>
> How can we guarantee that latest version of a newly added platform 
> supports all the same plugins of the previously added platforms?
>
> I think ultimately the only benefit is to give us some flexibility 
> with release schedules, but I would much rather have us focus on just 
> releasing everything more often.  Historically we have never been able 
> to deliver a patched point release in under a month, so assuming we 
> can get back to releasing every month, all would be fine, and the 
> train could just keep rolling forwards. Predictably!
>
>
>
>
> @purplecabbage
> risingj.com
>
>
> On Wed, Jul 23, 2014 at 10:59 AM, Parashuram Narasimhan (MS OPEN TECH) 
> < panarasi@microsoft.com> wrote:
>
> > I was thinking platforms are devDependencies and plugins are 
> > dependencies
> > :)
> >
> > In a way, that’s how the bundling works - plugins are packaged with 
> > the app, while platforms are only needed during development !!
> >
> > -----Original Message-----
> > From: Anis KADRI [mailto:anis.kadri@gmail.com]
> > Sent: Wednesday, July 23, 2014 10:54 AM
> > To: dev@cordova.apache.org
> > Subject: Re: Proposal: remove platform versions from platfroms.js
> >
> > +1 for package.json for platforms. plugins might a bit trickier but 
> > +still
> > doable, we could get rid of plugins/ but we somehow need to keep 
> > track of them in node_modules/ (maybe use one of the 10 config files we have).
> > Platforms in package.json should cause no problems though, 
> > add/remove platforms, pin/unpin versions if required.
> >
> >
> > On Wed, Jul 23, 2014 at 7:36 AM, Michal Mocny <mm...@chromium.org>
> wrote:
> >
> > > This sounds like a great topic for hangout Friday.  Glad to have a 
> > > concrete proposal / some counter arguments to discuss.
> > >
> > >
> > > On Wed, Jul 23, 2014 at 10:22 AM, Mark Koudritsky 
> > > <ka...@google.com>
> > > wrote:
> > >
> > > > >
> > > > > Currently WebWorks ships specific versions of things.
> > > > > If we had shipped unpinned versions of stuff, then eventually 
> > > > > we would have created projects which our UI wouldn't have 
> > > > > recognized as valid (because, they e.g. Didn't have a 
> > > > > ".cordova", or a "hooks", or a
> > > "merges"
> > > > > or whichever things we had been using to determine if a 
> > > > > project was
> > > > valid).
> > > > >
> > > >
> > > > As long as you continue to ship a version of cordova-backberry 
> > > > bundled
> > > with
> > > > WebWorks, it won't be affected by the change I propose. CLI will 
> > > > use that bundled version just like it does now using the 
> > > > settings in .cordova/config.json. We do the same thing with cca.
> > > >
> > > > If in the future you decide to stop bundling cordova-blackberry 
> > > > with WebWorks and switch to the npm published versions, I see 
> > > > several good
> > > ways
> > > > for doing that, but in any case, you will probably want to 
> > > > expose the version (or range of versions) to use as a user editable setting.
> > > >
> > >
> >
>

Re: Proposal: remove platform versions from platfroms.js

Posted by Andrew Grieve <ag...@chromium.org>.
I agree that the feature will make installing platforms less predictable...
or at least, just as unpredictable as plugins.

It is a good idea to look at exactly what the benefits are though.

First - the benefits of removing the idea of a "cadence version":
- Android 4.0 is on the horizon, maybe iOS 4.0 as well. Does this mean that
when they are ready, we should force all platforms to jump to 4.0? Wouldn't
be too bad...
- But once at 4.0, what if Windows or Blackberry requires a major release a
couple months later, move all platforms to 5.0?
- What if Android undergoes a lot of churn come 4.0, and wants to do 3 more
bugfix releases within the first month after? Do we force all platform's
versions to be updated? If not, what does the cadence number on CLI look
like?
- Cadence versioning forces us to try and release multiple platforms at the
same time.
  - E.g. Jesse wants to release windows, but has been waiting for Android
to be ready.
  - If each platform just released when it was ready, and had separate blog
posts, I think we'd have a happier release process, and would release more
often.

Now, we could do away with cadence version and still have CLI use the
version in its platforms.js file for each platform. So what does this
specific change of removing the pinning buy us?
- It will lighten the load of doing platform releases.
- It will make platforms and plugins both work in the same way.




On Wed, Jul 23, 2014 at 2:49 PM, Jesse <pu...@gmail.com> wrote:

> I agree, there are many cases where this will lead to complete
> un-predictability, and it is still unclear who this 'feature' benefits.
>
> How can we guarantee that latest version of a newly added platform supports
> all the same plugins of the previously added platforms?
>
> I think ultimately the only benefit is to give us some flexibility with
> release schedules, but I would much rather have us focus on just releasing
> everything more often.  Historically we have never been able to deliver a
> patched point release in under a month, so assuming we can get back to
> releasing every month, all would be fine, and the train could just keep
> rolling forwards. Predictably!
>
>
>
>
> @purplecabbage
> risingj.com
>
>
> On Wed, Jul 23, 2014 at 10:59 AM, Parashuram Narasimhan (MS OPEN TECH) <
> panarasi@microsoft.com> wrote:
>
> > I was thinking platforms are devDependencies and plugins are dependencies
> > :)
> >
> > In a way, that’s how the bundling works - plugins are packaged with the
> > app, while platforms are only needed during development !!
> >
> > -----Original Message-----
> > From: Anis KADRI [mailto:anis.kadri@gmail.com]
> > Sent: Wednesday, July 23, 2014 10:54 AM
> > To: dev@cordova.apache.org
> > Subject: Re: Proposal: remove platform versions from platfroms.js
> >
> > +1 for package.json for platforms. plugins might a bit trickier but
> > +still
> > doable, we could get rid of plugins/ but we somehow need to keep track of
> > them in node_modules/ (maybe use one of the 10 config files we have).
> > Platforms in package.json should cause no problems though, add/remove
> > platforms, pin/unpin versions if required.
> >
> >
> > On Wed, Jul 23, 2014 at 7:36 AM, Michal Mocny <mm...@chromium.org>
> wrote:
> >
> > > This sounds like a great topic for hangout Friday.  Glad to have a
> > > concrete proposal / some counter arguments to discuss.
> > >
> > >
> > > On Wed, Jul 23, 2014 at 10:22 AM, Mark Koudritsky <ka...@google.com>
> > > wrote:
> > >
> > > > >
> > > > > Currently WebWorks ships specific versions of things.
> > > > > If we had shipped unpinned versions of stuff, then eventually we
> > > > > would have created projects which our UI wouldn't have recognized
> > > > > as valid (because, they e.g. Didn't have a ".cordova", or a
> > > > > "hooks", or a
> > > "merges"
> > > > > or whichever things we had been using to determine if a project
> > > > > was
> > > > valid).
> > > > >
> > > >
> > > > As long as you continue to ship a version of cordova-backberry
> > > > bundled
> > > with
> > > > WebWorks, it won't be affected by the change I propose. CLI will use
> > > > that bundled version just like it does now using the settings in
> > > > .cordova/config.json. We do the same thing with cca.
> > > >
> > > > If in the future you decide to stop bundling cordova-blackberry with
> > > > WebWorks and switch to the npm published versions, I see several
> > > > good
> > > ways
> > > > for doing that, but in any case, you will probably want to expose
> > > > the version (or range of versions) to use as a user editable setting.
> > > >
> > >
> >
>

Re: Proposal: remove platform versions from platfroms.js

Posted by Andrew Grieve <ag...@chromium.org>.
If you're interested in this I think it'd be best to look at the
--experimental "plugin save" and "plugin restore" commands and try to
iterate from there.


On Wed, Jul 23, 2014 at 5:21 PM, Carlos Santana <cs...@gmail.com>
wrote:

> +1 on removing the pining
>
> Can we at least record what's get's installed in a single place?
> This will help if someone is trying to debug a problem, it will be easy to
> tell what are the components and their levels being use.
>
> Meaning a the minimum recording platforms, plugins, and latest cli version
> used on the project.
> Meaning every time you add a platform or plugin update cordova.json,
> everytime you run a cordova command like "cordova prepare"
> cordova.json
> {
> cordova: "3.7.1-0.3.7",
>
> platforms:[{name:"cordova-ios",version:"3.6.1"},{name:"cordova-blackberry",version:"3.7"}]
>
> plugins:[{id:"org.apache.cordova.console",version:"0.1.2"},{id:"com.ibm.myplugin",version:"0.1.1"}]
> }
>
> I prefer cordova.json on the root, and if not present look for a "cordova"
> object in package.json
>
> After this is done, we can discuss how this information can be use by the
> tool if at all like implementing a "cordova install" that reads the file,
> or a "cordova outdated" that reads the file, and so on.. of course without
> re implementing the wheel and leveraging "npm" and "node_modules" directory
>
> Also work towards making the cli so so unaware about the platforms, that
> adding a new platform "cordova-xphone" the cli will not need to change.
> Then the problem about what cli version works with what version of the
> platform becomes a mute point.
>
>
>
>
> On Wed, Jul 23, 2014 at 4:50 PM, Michal Mocny <mm...@chromium.org> wrote:
>
> > I think Mark summarizes my thoughts as well.
> >
> > We're overdue brainstorming what we want cordova workspaces to look like
> > (package.json, app manifests / config files, grunt/gulp integration,
> > browserify, directory structure..).  I don't think even the full hour on
> > this weeks hangout would suffice for this, so we should probably organize
> > something specifically for this topic for another date.  I don't think we
> > should be making any significant changes to users' cli workflow until we
> > figure out where we actually want to end up (and worry thats what we are
> > doing with the current package.json proposals).
> >
> > For the purpose of this week we should have the goal of figuring out:
> > - What behaviour do users expect (Please not "what is the current
> behaviour
> > and why it cannot change")
> > - How to simplify releasing platforms
> > - How/when to (properly) pin down versions of all cordova bits
> >
> > -Michal
> >
> >
> > On Wed, Jul 23, 2014 at 4:30 PM, Mark Koudritsky <ka...@google.com>
> > wrote:
> >
> > > Part of the discussion is release flexibility vs predictability. My
> main
> > > problem is that currently we have neither. By default CLI downloads
> > pinned
> > > versions of platforms but latest versions of plugins.
> > >
> > > Changing the concept of corodva project to something managed by npm is
> an
> > > interesting idea but it requires much much more than just adding a
> > > package.json file and is not a short term thing. I think it deserves a
> > > separate discussion.
> > >
> >
>
>
>
> --
> Carlos Santana
> <cs...@gmail.com>
>

Re: Proposal: remove platform versions from platfroms.js

Posted by Andrew Grieve <ag...@chromium.org>.
Hey Chuck, thanks for joining the conversation! Great to have all
stakeholders taking part.


On Wed, Jul 23, 2014 at 9:40 PM, Chuck Lantz <cl...@microsoft.com> wrote:

> Hey folks, I'm on the Visual Studio team.  I think my primary concern here
> comes more from what we expect developers to understand and the loss of
> predictability.  If you go to the Cordova documentation and see "Cordova
> 3.5.0", and then grab the CLI, that comes with a certain set of
> assumptions.  A Cordova version is very much a "thing" right now even if
> the pieces and parts underneath are much more independent.  So, as a
> developer, my frame of reference when I go and grab Cordova tools and add
> 3.5.0, I get 3.5.0 for each platform I add.  If I then go create another
> project, I'd expect to get the exact same thing - bugs and all.  If we lose
> that as an anchor concept, I think we'll quickly loose developers new to
> the ecosystem.  (Note that from a pure VS perspective, we could layer a
> concept on top to solve this if required as Andrew pointed out.)
>

I completely agree that by dropping the idea of a Cadence Version, that we
do lose a nicety. The question in my mind is whether the advantages make it
worth it.

For docs, it's easy enough to stop generating "versioned" docs, and just be
sure to keep them up to date with "Added in Android 4.0", "Removed in iOS
3.6" kind of messages.


>
> Now, even pinning to 3.5 and ignoring ".0" has issues since platforms can
> version independently and likely with little notice from a developer
> standpoint.  Even if a platform update just fixes a bug, it hurts
> predictability.  Devs will end up trying to figure out why a problem
> happens in one of their 3.5.0 projects and not the other.  Regressions can
> also happen, so new problems can surface on a newer project which I think
> is equally confusing.
>

To Mark's point, how are platforms different from plugins? Right now CLI
pulls latest plugin versions by default, so how do you deal with that re:
predictability?


>
> To be clear, I love idea of being able to pull newer versions of a
> platform and I definitely would love to see fixes be released faster.
>  However, I not see that 3.5.0-0.2.6 was allowing you to do "platform add
> android@3.5.1"?
>

Hmm, "platform add android@3.5.0" works fine using CLI@master. @3.5.1
wouldn't work because there is no 3.5.1 yet.








>
> -Chuck
>
> -----Original Message-----
> From: Carlos Santana [mailto:csantana23@gmail.com]
> Sent: Wednesday, July 23, 2014 2:27 PM
> To: dev@cordova.apache.org
> Subject: Re: Proposal: remove platform versions from platfroms.js
>
> I forgot to mention but agree with suggestion of having a local version of
> cordova cli saved in node_modues, and that the default cordova behavior
> will be to look first in local node_modules for cordova cli and if it found
> use that one, if not then use global one. same as grunt-cli
>
>
>
> On Wed, Jul 23, 2014 at 5:21 PM, Carlos Santana <cs...@gmail.com>
> wrote:
>
> > +1 on removing the pining
> >
> > Can we at least record what's get's installed in a single place?
> > This will help if someone is trying to debug a problem, it will be
> > easy to tell what are the components and their levels being use.
> >
> > Meaning a the minimum recording platforms, plugins, and latest cli
> > version used on the project.
> > Meaning every time you add a platform or plugin update cordova.json,
> > everytime you run a cordova command like "cordova prepare"
> > cordova.json
> > {
> > cordova: "3.7.1-0.3.7",
> >
> > platforms:[{name:"cordova-ios",version:"3.6.1"},{name:"cordova-blackbe
> > rry",version:"3.7"}]
> >
> > plugins:[{id:"org.apache.cordova.console",version:"0.1.2"},{id:"com.ib
> > m.myplugin",version:"0.1.1"}]
> > }
> >
> > I prefer cordova.json on the root, and if not present look for a
> "cordova"
> > object in package.json
> >
> > After this is done, we can discuss how this information can be use by
> > the tool if at all like implementing a "cordova install" that reads
> > the file, or a "cordova outdated" that reads the file, and so on.. of
> > course without re implementing the wheel and leveraging "npm" and
> > "node_modules" directory
> >
> > Also work towards making the cli so so unaware about the platforms,
> > that adding a new platform "cordova-xphone" the cli will not need to
> change.
> > Then the problem about what cli version works with what version of the
> > platform becomes a mute point.
> >
> >
> >
> >
> > On Wed, Jul 23, 2014 at 4:50 PM, Michal Mocny <mm...@chromium.org>
> wrote:
> >
> >> I think Mark summarizes my thoughts as well.
> >>
> >> We're overdue brainstorming what we want cordova workspaces to look
> >> like (package.json, app manifests / config files, grunt/gulp
> >> integration, browserify, directory structure..).  I don't think even
> >> the full hour on this weeks hangout would suffice for this, so we
> >> should probably organize something specifically for this topic for
> >> another date.  I don't think we should be making any significant
> >> changes to users' cli workflow until we figure out where we actually
> >> want to end up (and worry thats what we are doing with the current
> package.json proposals).
> >>
> >> For the purpose of this week we should have the goal of figuring out:
> >> - What behaviour do users expect (Please not "what is the current
> >> behaviour and why it cannot change")
> >> - How to simplify releasing platforms
> >> - How/when to (properly) pin down versions of all cordova bits
> >>
> >> -Michal
> >>
> >>
> >> On Wed, Jul 23, 2014 at 4:30 PM, Mark Koudritsky <ka...@google.com>
> >> wrote:
> >>
> >> > Part of the discussion is release flexibility vs predictability. My
> >> > main problem is that currently we have neither. By default CLI
> >> > downloads
> >> pinned
> >> > versions of platforms but latest versions of plugins.
> >> >
> >> > Changing the concept of corodva project to something managed by npm
> >> > is
> >> an
> >> > interesting idea but it requires much much more than just adding a
> >> > package.json file and is not a short term thing. I think it
> >> > deserves a separate discussion.
> >> >
> >>
> >
> >
> >
> > --
> > Carlos Santana
> > <cs...@gmail.com>
> >
>
>
>
> --
> Carlos Santana
> <cs...@gmail.com>
>

RE: Proposal: remove platform versions from platfroms.js

Posted by Chuck Lantz <cl...@microsoft.com>.
Hey folks, I'm on the Visual Studio team.  I think my primary concern here comes more from what we expect developers to understand and the loss of predictability.  If you go to the Cordova documentation and see "Cordova 3.5.0", and then grab the CLI, that comes with a certain set of assumptions.  A Cordova version is very much a "thing" right now even if the pieces and parts underneath are much more independent.  So, as a developer, my frame of reference when I go and grab Cordova tools and add 3.5.0, I get 3.5.0 for each platform I add.  If I then go create another project, I'd expect to get the exact same thing - bugs and all.  If we lose that as an anchor concept, I think we'll quickly loose developers new to the ecosystem.  (Note that from a pure VS perspective, we could layer a concept on top to solve this if required as Andrew pointed out.)

Now, even pinning to 3.5 and ignoring ".0" has issues since platforms can version independently and likely with little notice from a developer standpoint.  Even if a platform update just fixes a bug, it hurts predictability.  Devs will end up trying to figure out why a problem happens in one of their 3.5.0 projects and not the other.  Regressions can also happen, so new problems can surface on a newer project which I think is equally confusing.

To be clear, I love idea of being able to pull newer versions of a platform and I definitely would love to see fixes be released faster.  However, I not see that 3.5.0-0.2.6 was allowing you to do "platform add android@3.5.1"?

-Chuck

-----Original Message-----
From: Carlos Santana [mailto:csantana23@gmail.com] 
Sent: Wednesday, July 23, 2014 2:27 PM
To: dev@cordova.apache.org
Subject: Re: Proposal: remove platform versions from platfroms.js

I forgot to mention but agree with suggestion of having a local version of cordova cli saved in node_modues, and that the default cordova behavior will be to look first in local node_modules for cordova cli and if it found use that one, if not then use global one. same as grunt-cli



On Wed, Jul 23, 2014 at 5:21 PM, Carlos Santana <cs...@gmail.com>
wrote:

> +1 on removing the pining
>
> Can we at least record what's get's installed in a single place?
> This will help if someone is trying to debug a problem, it will be 
> easy to tell what are the components and their levels being use.
>
> Meaning a the minimum recording platforms, plugins, and latest cli 
> version used on the project.
> Meaning every time you add a platform or plugin update cordova.json, 
> everytime you run a cordova command like "cordova prepare"
> cordova.json
> {
> cordova: "3.7.1-0.3.7",
>
> platforms:[{name:"cordova-ios",version:"3.6.1"},{name:"cordova-blackbe
> rry",version:"3.7"}]
>
> plugins:[{id:"org.apache.cordova.console",version:"0.1.2"},{id:"com.ib
> m.myplugin",version:"0.1.1"}]
> }
>
> I prefer cordova.json on the root, and if not present look for a "cordova"
> object in package.json
>
> After this is done, we can discuss how this information can be use by 
> the tool if at all like implementing a "cordova install" that reads 
> the file, or a "cordova outdated" that reads the file, and so on.. of 
> course without re implementing the wheel and leveraging "npm" and 
> "node_modules" directory
>
> Also work towards making the cli so so unaware about the platforms, 
> that adding a new platform "cordova-xphone" the cli will not need to change.
> Then the problem about what cli version works with what version of the 
> platform becomes a mute point.
>
>
>
>
> On Wed, Jul 23, 2014 at 4:50 PM, Michal Mocny <mm...@chromium.org> wrote:
>
>> I think Mark summarizes my thoughts as well.
>>
>> We're overdue brainstorming what we want cordova workspaces to look 
>> like (package.json, app manifests / config files, grunt/gulp 
>> integration, browserify, directory structure..).  I don't think even 
>> the full hour on this weeks hangout would suffice for this, so we 
>> should probably organize something specifically for this topic for 
>> another date.  I don't think we should be making any significant 
>> changes to users' cli workflow until we figure out where we actually 
>> want to end up (and worry thats what we are doing with the current package.json proposals).
>>
>> For the purpose of this week we should have the goal of figuring out:
>> - What behaviour do users expect (Please not "what is the current 
>> behaviour and why it cannot change")
>> - How to simplify releasing platforms
>> - How/when to (properly) pin down versions of all cordova bits
>>
>> -Michal
>>
>>
>> On Wed, Jul 23, 2014 at 4:30 PM, Mark Koudritsky <ka...@google.com>
>> wrote:
>>
>> > Part of the discussion is release flexibility vs predictability. My 
>> > main problem is that currently we have neither. By default CLI 
>> > downloads
>> pinned
>> > versions of platforms but latest versions of plugins.
>> >
>> > Changing the concept of corodva project to something managed by npm 
>> > is
>> an
>> > interesting idea but it requires much much more than just adding a 
>> > package.json file and is not a short term thing. I think it 
>> > deserves a separate discussion.
>> >
>>
>
>
>
> --
> Carlos Santana
> <cs...@gmail.com>
>



--
Carlos Santana
<cs...@gmail.com>

Re: Proposal: remove platform versions from platfroms.js

Posted by Carlos Santana <cs...@gmail.com>.
I forgot to mention but agree with suggestion of having a local version of
cordova cli saved in node_modues, and that the default cordova behavior
will be to look first in local node_modules for cordova cli and if it found
use that one, if not then use global one. same as grunt-cli



On Wed, Jul 23, 2014 at 5:21 PM, Carlos Santana <cs...@gmail.com>
wrote:

> +1 on removing the pining
>
> Can we at least record what's get's installed in a single place?
> This will help if someone is trying to debug a problem, it will be easy to
> tell what are the components and their levels being use.
>
> Meaning a the minimum recording platforms, plugins, and latest cli version
> used on the project.
> Meaning every time you add a platform or plugin update cordova.json,
> everytime you run a cordova command like "cordova prepare"
> cordova.json
> {
> cordova: "3.7.1-0.3.7",
>
> platforms:[{name:"cordova-ios",version:"3.6.1"},{name:"cordova-blackberry",version:"3.7"}]
>
> plugins:[{id:"org.apache.cordova.console",version:"0.1.2"},{id:"com.ibm.myplugin",version:"0.1.1"}]
> }
>
> I prefer cordova.json on the root, and if not present look for a "cordova"
> object in package.json
>
> After this is done, we can discuss how this information can be use by the
> tool if at all like implementing a "cordova install" that reads the file,
> or a "cordova outdated" that reads the file, and so on.. of course without
> re implementing the wheel and leveraging "npm" and "node_modules" directory
>
> Also work towards making the cli so so unaware about the platforms, that
> adding a new platform "cordova-xphone" the cli will not need to change.
> Then the problem about what cli version works with what version of the
> platform becomes a mute point.
>
>
>
>
> On Wed, Jul 23, 2014 at 4:50 PM, Michal Mocny <mm...@chromium.org> wrote:
>
>> I think Mark summarizes my thoughts as well.
>>
>> We're overdue brainstorming what we want cordova workspaces to look like
>> (package.json, app manifests / config files, grunt/gulp integration,
>> browserify, directory structure..).  I don't think even the full hour on
>> this weeks hangout would suffice for this, so we should probably organize
>> something specifically for this topic for another date.  I don't think we
>> should be making any significant changes to users' cli workflow until we
>> figure out where we actually want to end up (and worry thats what we are
>> doing with the current package.json proposals).
>>
>> For the purpose of this week we should have the goal of figuring out:
>> - What behaviour do users expect (Please not "what is the current
>> behaviour
>> and why it cannot change")
>> - How to simplify releasing platforms
>> - How/when to (properly) pin down versions of all cordova bits
>>
>> -Michal
>>
>>
>> On Wed, Jul 23, 2014 at 4:30 PM, Mark Koudritsky <ka...@google.com>
>> wrote:
>>
>> > Part of the discussion is release flexibility vs predictability. My main
>> > problem is that currently we have neither. By default CLI downloads
>> pinned
>> > versions of platforms but latest versions of plugins.
>> >
>> > Changing the concept of corodva project to something managed by npm is
>> an
>> > interesting idea but it requires much much more than just adding a
>> > package.json file and is not a short term thing. I think it deserves a
>> > separate discussion.
>> >
>>
>
>
>
> --
> Carlos Santana
> <cs...@gmail.com>
>



-- 
Carlos Santana
<cs...@gmail.com>

Re: Proposal: remove platform versions from platfroms.js

Posted by Carlos Santana <cs...@gmail.com>.
+1 on removing the pining

Can we at least record what's get's installed in a single place?
This will help if someone is trying to debug a problem, it will be easy to
tell what are the components and their levels being use.

Meaning a the minimum recording platforms, plugins, and latest cli version
used on the project.
Meaning every time you add a platform or plugin update cordova.json,
everytime you run a cordova command like "cordova prepare"
cordova.json
{
cordova: "3.7.1-0.3.7",
platforms:[{name:"cordova-ios",version:"3.6.1"},{name:"cordova-blackberry",version:"3.7"}]
plugins:[{id:"org.apache.cordova.console",version:"0.1.2"},{id:"com.ibm.myplugin",version:"0.1.1"}]
}

I prefer cordova.json on the root, and if not present look for a "cordova"
object in package.json

After this is done, we can discuss how this information can be use by the
tool if at all like implementing a "cordova install" that reads the file,
or a "cordova outdated" that reads the file, and so on.. of course without
re implementing the wheel and leveraging "npm" and "node_modules" directory

Also work towards making the cli so so unaware about the platforms, that
adding a new platform "cordova-xphone" the cli will not need to change.
Then the problem about what cli version works with what version of the
platform becomes a mute point.




On Wed, Jul 23, 2014 at 4:50 PM, Michal Mocny <mm...@chromium.org> wrote:

> I think Mark summarizes my thoughts as well.
>
> We're overdue brainstorming what we want cordova workspaces to look like
> (package.json, app manifests / config files, grunt/gulp integration,
> browserify, directory structure..).  I don't think even the full hour on
> this weeks hangout would suffice for this, so we should probably organize
> something specifically for this topic for another date.  I don't think we
> should be making any significant changes to users' cli workflow until we
> figure out where we actually want to end up (and worry thats what we are
> doing with the current package.json proposals).
>
> For the purpose of this week we should have the goal of figuring out:
> - What behaviour do users expect (Please not "what is the current behaviour
> and why it cannot change")
> - How to simplify releasing platforms
> - How/when to (properly) pin down versions of all cordova bits
>
> -Michal
>
>
> On Wed, Jul 23, 2014 at 4:30 PM, Mark Koudritsky <ka...@google.com>
> wrote:
>
> > Part of the discussion is release flexibility vs predictability. My main
> > problem is that currently we have neither. By default CLI downloads
> pinned
> > versions of platforms but latest versions of plugins.
> >
> > Changing the concept of corodva project to something managed by npm is an
> > interesting idea but it requires much much more than just adding a
> > package.json file and is not a short term thing. I think it deserves a
> > separate discussion.
> >
>



-- 
Carlos Santana
<cs...@gmail.com>

Re: Proposal: remove platform versions from platfroms.js

Posted by Michal Mocny <mm...@chromium.org>.
I think Mark summarizes my thoughts as well.

We're overdue brainstorming what we want cordova workspaces to look like
(package.json, app manifests / config files, grunt/gulp integration,
browserify, directory structure..).  I don't think even the full hour on
this weeks hangout would suffice for this, so we should probably organize
something specifically for this topic for another date.  I don't think we
should be making any significant changes to users' cli workflow until we
figure out where we actually want to end up (and worry thats what we are
doing with the current package.json proposals).

For the purpose of this week we should have the goal of figuring out:
- What behaviour do users expect (Please not "what is the current behaviour
and why it cannot change")
- How to simplify releasing platforms
- How/when to (properly) pin down versions of all cordova bits

-Michal


On Wed, Jul 23, 2014 at 4:30 PM, Mark Koudritsky <ka...@google.com> wrote:

> Part of the discussion is release flexibility vs predictability. My main
> problem is that currently we have neither. By default CLI downloads pinned
> versions of platforms but latest versions of plugins.
>
> Changing the concept of corodva project to something managed by npm is an
> interesting idea but it requires much much more than just adding a
> package.json file and is not a short term thing. I think it deserves a
> separate discussion.
>

Re: Proposal: remove platform versions from platfroms.js

Posted by Mark Koudritsky <ka...@google.com>.
Part of the discussion is release flexibility vs predictability. My main
problem is that currently we have neither. By default CLI downloads pinned
versions of platforms but latest versions of plugins.

Changing the concept of corodva project to something managed by npm is an
interesting idea but it requires much much more than just adding a
package.json file and is not a short term thing. I think it deserves a
separate discussion.

Re: Proposal: remove platform versions from platfroms.js

Posted by Jesse <pu...@gmail.com>.
I agree, there are many cases where this will lead to complete
un-predictability, and it is still unclear who this 'feature' benefits.

How can we guarantee that latest version of a newly added platform supports
all the same plugins of the previously added platforms?

I think ultimately the only benefit is to give us some flexibility with
release schedules, but I would much rather have us focus on just releasing
everything more often.  Historically we have never been able to deliver a
patched point release in under a month, so assuming we can get back to
releasing every month, all would be fine, and the train could just keep
rolling forwards. Predictably!




@purplecabbage
risingj.com


On Wed, Jul 23, 2014 at 10:59 AM, Parashuram Narasimhan (MS OPEN TECH) <
panarasi@microsoft.com> wrote:

> I was thinking platforms are devDependencies and plugins are dependencies
> :)
>
> In a way, that’s how the bundling works - plugins are packaged with the
> app, while platforms are only needed during development !!
>
> -----Original Message-----
> From: Anis KADRI [mailto:anis.kadri@gmail.com]
> Sent: Wednesday, July 23, 2014 10:54 AM
> To: dev@cordova.apache.org
> Subject: Re: Proposal: remove platform versions from platfroms.js
>
> +1 for package.json for platforms. plugins might a bit trickier but
> +still
> doable, we could get rid of plugins/ but we somehow need to keep track of
> them in node_modules/ (maybe use one of the 10 config files we have).
> Platforms in package.json should cause no problems though, add/remove
> platforms, pin/unpin versions if required.
>
>
> On Wed, Jul 23, 2014 at 7:36 AM, Michal Mocny <mm...@chromium.org> wrote:
>
> > This sounds like a great topic for hangout Friday.  Glad to have a
> > concrete proposal / some counter arguments to discuss.
> >
> >
> > On Wed, Jul 23, 2014 at 10:22 AM, Mark Koudritsky <ka...@google.com>
> > wrote:
> >
> > > >
> > > > Currently WebWorks ships specific versions of things.
> > > > If we had shipped unpinned versions of stuff, then eventually we
> > > > would have created projects which our UI wouldn't have recognized
> > > > as valid (because, they e.g. Didn't have a ".cordova", or a
> > > > "hooks", or a
> > "merges"
> > > > or whichever things we had been using to determine if a project
> > > > was
> > > valid).
> > > >
> > >
> > > As long as you continue to ship a version of cordova-backberry
> > > bundled
> > with
> > > WebWorks, it won't be affected by the change I propose. CLI will use
> > > that bundled version just like it does now using the settings in
> > > .cordova/config.json. We do the same thing with cca.
> > >
> > > If in the future you decide to stop bundling cordova-blackberry with
> > > WebWorks and switch to the npm published versions, I see several
> > > good
> > ways
> > > for doing that, but in any case, you will probably want to expose
> > > the version (or range of versions) to use as a user editable setting.
> > >
> >
>

RE: Proposal: remove platform versions from platfroms.js

Posted by "Parashuram Narasimhan (MS OPEN TECH)" <pa...@microsoft.com>.
I was thinking platforms are devDependencies and plugins are dependencies :) 

In a way, that’s how the bundling works - plugins are packaged with the app, while platforms are only needed during development !!

-----Original Message-----
From: Anis KADRI [mailto:anis.kadri@gmail.com] 
Sent: Wednesday, July 23, 2014 10:54 AM
To: dev@cordova.apache.org
Subject: Re: Proposal: remove platform versions from platfroms.js

+1 for package.json for platforms. plugins might a bit trickier but 
+still
doable, we could get rid of plugins/ but we somehow need to keep track of them in node_modules/ (maybe use one of the 10 config files we have).
Platforms in package.json should cause no problems though, add/remove platforms, pin/unpin versions if required.


On Wed, Jul 23, 2014 at 7:36 AM, Michal Mocny <mm...@chromium.org> wrote:

> This sounds like a great topic for hangout Friday.  Glad to have a 
> concrete proposal / some counter arguments to discuss.
>
>
> On Wed, Jul 23, 2014 at 10:22 AM, Mark Koudritsky <ka...@google.com>
> wrote:
>
> > >
> > > Currently WebWorks ships specific versions of things.
> > > If we had shipped unpinned versions of stuff, then eventually we 
> > > would have created projects which our UI wouldn't have recognized 
> > > as valid (because, they e.g. Didn't have a ".cordova", or a 
> > > "hooks", or a
> "merges"
> > > or whichever things we had been using to determine if a project 
> > > was
> > valid).
> > >
> >
> > As long as you continue to ship a version of cordova-backberry 
> > bundled
> with
> > WebWorks, it won't be affected by the change I propose. CLI will use 
> > that bundled version just like it does now using the settings in 
> > .cordova/config.json. We do the same thing with cca.
> >
> > If in the future you decide to stop bundling cordova-blackberry with 
> > WebWorks and switch to the npm published versions, I see several 
> > good
> ways
> > for doing that, but in any case, you will probably want to expose 
> > the version (or range of versions) to use as a user editable setting.
> >
>

Re: Proposal: remove platform versions from platfroms.js

Posted by Anis KADRI <an...@gmail.com>.
+1 for package.json for platforms. plugins might a bit trickier but still
doable, we could get rid of plugins/ but we somehow need to keep track of
them in node_modules/ (maybe use one of the 10 config files we have).
Platforms in package.json should cause no problems though, add/remove
platforms, pin/unpin versions if required.


On Wed, Jul 23, 2014 at 7:36 AM, Michal Mocny <mm...@chromium.org> wrote:

> This sounds like a great topic for hangout Friday.  Glad to have a concrete
> proposal / some counter arguments to discuss.
>
>
> On Wed, Jul 23, 2014 at 10:22 AM, Mark Koudritsky <ka...@google.com>
> wrote:
>
> > >
> > > Currently WebWorks ships specific versions of things.
> > > If we had shipped unpinned versions of stuff, then eventually we would
> > > have created projects which our UI wouldn't have recognized as valid
> > > (because, they e.g. Didn't have a ".cordova", or a "hooks", or a
> "merges"
> > > or whichever things we had been using to determine if a project was
> > valid).
> > >
> >
> > As long as you continue to ship a version of cordova-backberry bundled
> with
> > WebWorks, it won't be affected by the change I propose. CLI will use that
> > bundled version just like it does now using the settings in
> > .cordova/config.json. We do the same thing with cca.
> >
> > If in the future you decide to stop bundling cordova-blackberry with
> > WebWorks and switch to the npm published versions, I see several good
> ways
> > for doing that, but in any case, you will probably want to expose the
> > version (or range of versions) to use as a user editable setting.
> >
>

RE: Proposal: remove platform versions from platfroms.js

Posted by "Parashuram Narasimhan (MS OPEN TECH)" <pa...@microsoft.com>.
I would not be able to join the Friday hangout, but here are my main concerns -

I agree that it would be best to always give the users the latest version of the platform and keeping it independent of the CLI. However, given that Cordova now also caters to enterprise users, backwards compatibility and reproducible dev environment. 
The question would be - what should be the default behavior? When a new user downloads the CLI and then creates a project, we could download the latest versions, but will they always be saved in the config.xml so that they can be restored? Does it not make more sense to semver them to ensure that breaking changes do not impact users who do not want to upgrade their projects? Asking users to change config.xml if they need to preserve platforms every time may not be a good default.  

Does this change also mean  that every release of the Cordova CLI will be tested against multiple versions of the platforms? 

In case of Visual Studio, a version of CLI is bundled with the tools and the user cannot choose any other version. This simplifies issues with support and is a guarantee that the specific version of the CLI works with a specific version of VS tools. Visual Studio and Cordova have different release timings and would it always be possible to guarantee that a newer version of the CLI works with an older version of the VS tools? 

-----Original Message-----
From: Jesse [mailto:purplecabbage@gmail.com] 
Sent: Wednesday, July 23, 2014 10:47 AM
To: dev@cordova.apache.org
Subject: Re: Proposal: remove platform versions from platfroms.js

Yeah, let's discuss the full impact on Friday.

@purplecabbage
risingj.com


On Wed, Jul 23, 2014 at 7:36 AM, Michal Mocny <mm...@chromium.org> wrote:

> This sounds like a great topic for hangout Friday.  Glad to have a 
> concrete proposal / some counter arguments to discuss.
>
>
> On Wed, Jul 23, 2014 at 10:22 AM, Mark Koudritsky <ka...@google.com>
> wrote:
>
> > >
> > > Currently WebWorks ships specific versions of things.
> > > If we had shipped unpinned versions of stuff, then eventually we 
> > > would have created projects which our UI wouldn't have recognized 
> > > as valid (because, they e.g. Didn't have a ".cordova", or a 
> > > "hooks", or a
> "merges"
> > > or whichever things we had been using to determine if a project 
> > > was
> > valid).
> > >
> >
> > As long as you continue to ship a version of cordova-backberry 
> > bundled
> with
> > WebWorks, it won't be affected by the change I propose. CLI will use 
> > that bundled version just like it does now using the settings in 
> > .cordova/config.json. We do the same thing with cca.
> >
> > If in the future you decide to stop bundling cordova-blackberry with 
> > WebWorks and switch to the npm published versions, I see several 
> > good
> ways
> > for doing that, but in any case, you will probably want to expose 
> > the version (or range of versions) to use as a user editable setting.
> >
>

Re: Proposal: remove platform versions from platfroms.js

Posted by Jesse <pu...@gmail.com>.
Yeah, let's discuss the full impact on Friday.

@purplecabbage
risingj.com


On Wed, Jul 23, 2014 at 7:36 AM, Michal Mocny <mm...@chromium.org> wrote:

> This sounds like a great topic for hangout Friday.  Glad to have a concrete
> proposal / some counter arguments to discuss.
>
>
> On Wed, Jul 23, 2014 at 10:22 AM, Mark Koudritsky <ka...@google.com>
> wrote:
>
> > >
> > > Currently WebWorks ships specific versions of things.
> > > If we had shipped unpinned versions of stuff, then eventually we would
> > > have created projects which our UI wouldn't have recognized as valid
> > > (because, they e.g. Didn't have a ".cordova", or a "hooks", or a
> "merges"
> > > or whichever things we had been using to determine if a project was
> > valid).
> > >
> >
> > As long as you continue to ship a version of cordova-backberry bundled
> with
> > WebWorks, it won't be affected by the change I propose. CLI will use that
> > bundled version just like it does now using the settings in
> > .cordova/config.json. We do the same thing with cca.
> >
> > If in the future you decide to stop bundling cordova-blackberry with
> > WebWorks and switch to the npm published versions, I see several good
> ways
> > for doing that, but in any case, you will probably want to expose the
> > version (or range of versions) to use as a user editable setting.
> >
>

Re: Proposal: remove platform versions from platfroms.js

Posted by Michal Mocny <mm...@chromium.org>.
This sounds like a great topic for hangout Friday.  Glad to have a concrete
proposal / some counter arguments to discuss.


On Wed, Jul 23, 2014 at 10:22 AM, Mark Koudritsky <ka...@google.com> wrote:

> >
> > Currently WebWorks ships specific versions of things.
> > If we had shipped unpinned versions of stuff, then eventually we would
> > have created projects which our UI wouldn't have recognized as valid
> > (because, they e.g. Didn't have a ".cordova", or a "hooks", or a "merges"
> > or whichever things we had been using to determine if a project was
> valid).
> >
>
> As long as you continue to ship a version of cordova-backberry bundled with
> WebWorks, it won't be affected by the change I propose. CLI will use that
> bundled version just like it does now using the settings in
> .cordova/config.json. We do the same thing with cca.
>
> If in the future you decide to stop bundling cordova-blackberry with
> WebWorks and switch to the npm published versions, I see several good ways
> for doing that, but in any case, you will probably want to expose the
> version (or range of versions) to use as a user editable setting.
>

Re: Proposal: remove platform versions from platfroms.js

Posted by Mark Koudritsky <ka...@google.com>.
>
> Currently WebWorks ships specific versions of things.
> If we had shipped unpinned versions of stuff, then eventually we would
> have created projects which our UI wouldn't have recognized as valid
> (because, they e.g. Didn't have a ".cordova", or a "hooks", or a "merges"
> or whichever things we had been using to determine if a project was valid).
>

As long as you continue to ship a version of cordova-backberry bundled with
WebWorks, it won't be affected by the change I propose. CLI will use that
bundled version just like it does now using the settings in
.cordova/config.json. We do the same thing with cca.

If in the future you decide to stop bundling cordova-blackberry with
WebWorks and switch to the npm published versions, I see several good ways
for doing that, but in any case, you will probably want to expose the
version (or range of versions) to use as a user editable setting.

Re: Proposal: remove platform versions from platfroms.js

Posted by Andrew Grieve <ag...@chromium.org>.
I'm definitely in favour of not pinning the version, since I think that
will significantly simplify the release process.

re webworks - not sure I fully understood the things you wanted to think
about there, but I'm sure it would be easy to have downstreams pin
versions. You can already override where CLI looks for platforms using
.cordova/config.json or the JS API equivalent.

re Visual Studio - again, I don't fully know how this integration works,
but sounds like right now your users can choose the version of CLI to use?
Instead - how about just always using the latest version of CLI and have
them choose the version of the platform to use?

re Recreating platforms - Gorkem added an experimental feature for saving &
restoring platforms to config.xml. I think it still needs a bit of work,
but I think this approach makes sense and we should pursue it.

re package.json - I think the idea definitely a good one, but I think our
tools pretty much already support this use-case via "cordova platform add
node_modules/cordova-android". Perhaps we could add the equivalent of
plugins_search_path for platforms so that it automatically looks within
node_modules? Either way - I like supporting this flow, but I don't think
we should move to only support it since it's easy to get what's in your
node_modules mismatching what's in your platforms/




On Tue, Jul 22, 2014 at 6:45 PM, Parashuram Narasimhan (MS OPEN TECH) <
panarasi@microsoft.com> wrote:

> Always downloading the latest will also be a problem for Visual Studio
> that uses Cordova as the IDE.
>
> We would need a way where if 2 developers checkout the project and use a
> specific version of Cordova (CLI), they should have the same version of
> platform too. Given that the version of the platforms is not picked up from
> any place in the project and is explicitly specified only in the CLI, this
> would be hard.
>
> If a user does not check in the platform versions, how will be they able
> to recreate the platforms again ?
>
> A random idea - how about we treat Cordova projects like a NodeJs project.
> Cordova is much like a "build system" (think Grunt). There is a
> package.json (another config file, sign :( ) that specifies the version of
> platforms and plugins that this Cordova platform needs. This would be like
> how Grunt version is specified in package.json. The Cordova-cli would be
> like Grunt-cli. This way, plugin and platforms can simply be installed
> using npm and are treated just like packages to "build" an app.
>
> -----Original Message-----
> From: Josh Soref [mailto:jsoref@blackberry.com]
> Sent: Tuesday, July 22, 2014 3:06 PM
> To: dev@cordova.apache.org
> Subject: Re: Proposal: remove platform versions from platfroms.js
>
> Mark Koudritsky wrote:
> >As the next step in decoupling platform releases I would like to remove
> >the hard-coded version in platform.js and let the CLI to download the
> >latest platform version available on npm by default.
>
> As long as the file will continue to support pinned versions…
>
> I'm not quite sure where I stand on this as a default behavior.
>
> Currently WebWorks ships specific versions of things.
> If we had shipped unpinned versions of stuff, then eventually we would
> have created projects which our UI wouldn't have recognized as valid
> (because, they e.g. Didn't have a ".cordova", or a "hooks", or a "merges"
> or whichever things we had been using to determine if a project was valid).
>
> The second version of the problem is that I'd sort of like to be able to
> /think/ about letting webworks users get newer versions of
> cordova-blackberry w/o necessarily having to install a new "webworks".
> (This is sort of the opposite of the previous one)
>
> The third, is that I might want to have distinct version series for
> webworks based things and cordova based things (I'm not really sure on this
> point).
>
> One approach is to rely on api versioning so instead of platform = 3.5 ->
> 3.6 -> 3.7, we could have platform = 3.5:3.5 -> 3.5:3.6, where the major
> number is a cli version. That would in theory let me offer different
> versions of the platform to a cli w/o giving it a version that will just
> break it.
>
> >- It will hit the network for every "platform add" that has no version
> >explicitly specified. In most cases the reply from npm will be an "HTTP
> >304
> >- Not Modified".
> > - We'll have to add in some sort of check that the version of CLI that
> >you have works with the platform. E.g. current tools might not work
> >with cordova-5.0. In than case we can display an error that instructs
> >the user to either upgrade CLI or specify the platform version
> >explicitly.
>
> Not a big fan of this "specify explicitly" nor "command line", webworks is
> often used w/ a GUI (well, we ship one, I'm not sure how often it's used…).
>
> WebWorks also ships its own version of cordova-blackberry, which isn't
> precisely the same as the version that's in the registry. I'm not sure I'd
> want to have to hit the network for this. At the very least, I'd like
> information about how to cache our version into the cache so at least
> something is present.
>
>

RE: Proposal: remove platform versions from platfroms.js

Posted by "Parashuram Narasimhan (MS OPEN TECH)" <pa...@microsoft.com>.
Always downloading the latest will also be a problem for Visual Studio that uses Cordova as the IDE. 

We would need a way where if 2 developers checkout the project and use a specific version of Cordova (CLI), they should have the same version of platform too. Given that the version of the platforms is not picked up from any place in the project and is explicitly specified only in the CLI, this would be hard. 

If a user does not check in the platform versions, how will be they able to recreate the platforms again ? 

A random idea - how about we treat Cordova projects like a NodeJs project. Cordova is much like a "build system" (think Grunt). There is a package.json (another config file, sign :( ) that specifies the version of platforms and plugins that this Cordova platform needs. This would be like how Grunt version is specified in package.json. The Cordova-cli would be like Grunt-cli. This way, plugin and platforms can simply be installed using npm and are treated just like packages to "build" an app. 

-----Original Message-----
From: Josh Soref [mailto:jsoref@blackberry.com] 
Sent: Tuesday, July 22, 2014 3:06 PM
To: dev@cordova.apache.org
Subject: Re: Proposal: remove platform versions from platfroms.js

Mark Koudritsky wrote:
>As the next step in decoupling platform releases I would like to remove 
>the hard-coded version in platform.js and let the CLI to download the 
>latest platform version available on npm by default.

As long as the file will continue to support pinned versions…

I'm not quite sure where I stand on this as a default behavior.

Currently WebWorks ships specific versions of things.
If we had shipped unpinned versions of stuff, then eventually we would have created projects which our UI wouldn't have recognized as valid (because, they e.g. Didn't have a ".cordova", or a "hooks", or a "merges"
or whichever things we had been using to determine if a project was valid).

The second version of the problem is that I'd sort of like to be able to /think/ about letting webworks users get newer versions of cordova-blackberry w/o necessarily having to install a new "webworks".
(This is sort of the opposite of the previous one)

The third, is that I might want to have distinct version series for webworks based things and cordova based things (I'm not really sure on this point).

One approach is to rely on api versioning so instead of platform = 3.5 ->
3.6 -> 3.7, we could have platform = 3.5:3.5 -> 3.5:3.6, where the major number is a cli version. That would in theory let me offer different versions of the platform to a cli w/o giving it a version that will just break it.

>- It will hit the network for every "platform add" that has no version 
>explicitly specified. In most cases the reply from npm will be an "HTTP
>304
>- Not Modified".
> - We'll have to add in some sort of check that the version of CLI that 
>you have works with the platform. E.g. current tools might not work 
>with cordova-5.0. In than case we can display an error that instructs 
>the user to either upgrade CLI or specify the platform version 
>explicitly.

Not a big fan of this "specify explicitly" nor "command line", webworks is often used w/ a GUI (well, we ship one, I'm not sure how often it's used…).

WebWorks also ships its own version of cordova-blackberry, which isn't precisely the same as the version that's in the registry. I'm not sure I'd want to have to hit the network for this. At the very least, I'd like information about how to cache our version into the cache so at least something is present.


Re: Proposal: remove platform versions from platfroms.js

Posted by Josh Soref <js...@blackberry.com>.
Mark Koudritsky wrote:
>As the next step in decoupling platform releases I would like to remove
>the
>hard-coded version in platform.js and let the CLI to download the latest
>platform version available on npm by default.

As long as the file will continue to support pinned versions…

I'm not quite sure where I stand on this as a default behavior.

Currently WebWorks ships specific versions of things.
If we had shipped unpinned versions of stuff, then eventually we would
have created projects which our UI wouldn't have recognized as valid
(because, they e.g. Didn't have a ".cordova", or a "hooks", or a "merges"
or whichever things we had been using to determine if a project was valid).

The second version of the problem is that I'd sort of like to be able to
/think/ about letting webworks users get newer versions of
cordova-blackberry w/o necessarily having to install a new "webworks".
(This is sort of the opposite of the previous one)

The third, is that I might want to have distinct version series for
webworks based things and cordova based things (I'm not really sure on
this point).

One approach is to rely on api versioning so instead of platform = 3.5 ->
3.6 -> 3.7, we could have platform = 3.5:3.5 -> 3.5:3.6, where the major
number is a cli version. That would in theory let me offer different
versions of the platform to a cli w/o giving it a version that will just
break it.

>- It will hit the network for every "platform add" that has no version
>explicitly specified. In most cases the reply from npm will be an "HTTP
>304
>- Not Modified".
> - We'll have to add in some sort of check that the version of CLI that
>you
>have works with the platform. E.g. current tools might not work with
>cordova-5.0. In than case we can display an error that instructs the user
>to either upgrade CLI or specify the platform version explicitly.

Not a big fan of this "specify explicitly" nor "command line", webworks is
often used w/ a GUI (well, we ship one, I'm not sure how often it's used…).

WebWorks also ships its own version of cordova-blackberry, which isn't
precisely the same as the version that's in the registry. I'm not sure I'd
want to have to hit the network for this. At the very least, I'd like
information about how to cache our version into the cache so at least
something is present.