[
https://issues.apache.org/jira/browse/CB-7659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14151999#comment-14151999
]
Steve Gill commented on CB-7659:
--------------------------------
Thanks for filing an issue Isaac!
We are actually planning on dropping the apache cordova version and just using
semver for the CLI from now on! Aiming to get this in for the next release!
> Use X.Y.Z versions instead of X.Y.Z-A.B.C for npm release
> ---------------------------------------------------------
>
> Key: CB-7659
> URL: https://issues.apache.org/jira/browse/CB-7659
> Project: Apache Cordova
> Issue Type: Bug
> Components: CLI
> Reporter: Isaac Z. Schlueter
>
> https://github.com/npm/node-semver/issues/103
> Cordova should be releasing using X.Y.Z versions, not X.Y.Z-A.B.C versions.
> According to the SemVer specification, the part after the - is a prerelease,
> and at the request of many in the npm community, we've stopped including
> prerelease versions in ranges unless they are explicitly opted in by
> including a prerelease in the version range itself.
> I understand that one of the versions is the version of "the cli" and the
> other is the version of "apache cordova". There are a few ways that other
> similar projects have handled this:
> - Create a "cordova36" project, and give it the version 1.2.1
> - Squash the cordova version into the first two digits, and the cli version
> into the third digit, so it'd be 36.1.121
> - Abandon putting the cordova version in the package name, and just solve it
> with documentation.
> - Separate the cli project into two npm packages, one of which depends on the
> other, and give them separate version numbers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
