In https://github.com/apache/cordova-lib/blob/master/src/platforms/platformsConfig.json Cordova "pins" a number of platforms to a specific version, that is used to install the platform is no other version is supplied. This behavior is also mentioned in several places in https://github.com/apache/cordova-coho/blob/master/docs/versioning-and-release-strategy.md.
The clear disadvantage of this behavior is that we need to do a release of `cordova-lib` (and `cordova-cli` that contains it) to update the pinned versions. Until then, people just running e.g. `cordova platform add android` will get an outdated version by default and (from experience on Stack Overflow, Ionic Forum and `support` issues here) have to be told regularly to update the platform when they encounter a bug (`cordova platform add [email protected]`) - it is just not really expected behavior for most users that the default command doesn't install the newest version. 1. Why do we need pinned versions? 1. What is the history behind this feature? 1. What are the advantages of it? 1. Does this behavior still make sense today? 1. Can we maybe get rid of it and replace it with "will install `latest` by default, but can of course still be overridden by supplying a specific version" in a future cli/lib version? [ Full content available at: https://github.com/apache/cordova/issues/18 ] This message was relayed via gitbox.apache.org for [email protected]
