This section describes how we store version numbers on our various repositories.
There are two aspects of this:
bin/create
script)For #1:
VERSION
file at the root of the repository.For #2:
cordova/version
script of a created project.VERSION
file at the time of creation.There are two aspects of this:
For #1:
VERSION
file at the root of the repository.For #2:
Plugins store their version within their plugin.xml file. No VERSION
files exist.
These tools are built as npm modules, and so use package.json. No VERSION
files exist.
This section describes how we __choose version numbers for each branch within our various repositories.
The version number should correspond closely to the git branch. When a release branch is made, both the branch and the master branch should be updated. The master branch should always have a version number ending in “-dev”, which indicates the version currently being developed. A fresh release branch should change the version to an “-rc1” version, and then change to the unqualified version number when it is released.
(This constant version number can be updated manually, but should eventually be updated via coho as release branches are made.)
This should give a rough idea how the version number should advance:
3.3.0-dev 3.2.0-dev| | | --A---B---C---D (master) \ \--E---F---G---H (3.2.x) | | | 3.2.0-rc1| 3.2.1-rc1 3.2.0
Current support:
||'''Platform'''||'''Support'''|| ||Android || {*} || ||BB10 || {o} || ||iOS || {o} || ||OSX || {o} || ||QT || {o} || ||Tizen || {o} || ||WebOS || {o} || ||Win || {o} || ||WP7 || {o} || ||WP8 || {o} || ||www || {o} ||
cordova-js follows the same scheme as platforms.
Current state is that we have master & dev branches. This is because plugman pulls from master by default, so it must remain stable.
cordova-plugman and cordova-cli follow the same scheme as platforms.