Michal Mocny wrote: >Thanks everyone for participation in what was a long and grueling >discussion. > >Summary of current proposal: >- Cad-ver is dead. >- Everything moves Sem-ver, with platforms continuing from current >versions >and diverging over time. >- CLI potentially gets a significant version bump to showcase this reset >(to 5.0 or 10.0, not yet settled) >- Pinning default platform versions *will* continue for the time being, >but >it will be trivial to override the default. >- Platforms will have CLI <engine> tag equivalent (unclear yet if as node >peerDependency or otherwise) so devs will know when they need to >upgrade/downgrade CLI for non-default platform versions. >- After a platform update, eventually CLI will release to "pin" the new >default, and bump its PATCH/MINOR version (unless CLI had a functional >update at same time that requires a larger bump). >- After you update CLI, your existing projects don't change & platform >upgrades remain explicit, but you will now get warnings if your installed >platforms are older than the CLI pinned versions. >- Event MAJOR changes to platforms are not MAJOR updates to the CLI, >unless >there is an actual breaking change to the CLI tool (i.e. new CLI will no >longer work with the currently installed platform). >- Platform and CLI docs have to split out and be released & versioned >alongside each (like plugins). Cross references from one to the other >will >only be needed in a few places. > > >Note: The CLI-Platform compatibility story is functionally no different >than we have today. If you upgrade your CLI and there is a breaking >change, you will have to re-create your projects or downgrade CLI again. >Now we plan to be more explicit about it and offer warnings. > >Note: There is no concept of a "fancy-pants" release other than to say >"latest as of Oct 2014" or something. Platforms don't have a single >common >set of functionality, so CadVer was somewhat misleading already in that >sense. We could introduce a concept of "API Level" for exec bridge or >something for use by plugins, but not sure that has value. > > >What wasn't covered that came to mind after the fact: >- When there is an update available for CLI, should we give a warning to >update? (this is useful, but isn't common for npm modules. I think we >already do this from plugman when you try to publish plugins?). > > >Did I miss anything?
I said I'd make a patch to document `cordova platform add android@3.7`, it's here: https://github.com/apache/cordova-cli/pull/195 Could people please help fix it so that it's sufficiently good? (I'm off tomorrow)
