Dear Wiki user, You have subscribed to a wiki page or wiki category on "Cordova Wiki" for change notification.
The "CordovaAndGit" page has been changed by AndrewGrieve: http://wiki.apache.org/cordova/CordovaAndGit New page: = Cordova and Git = Cordova repositories have two main branches: 1. master 2. next Transient branches that may exist: * Topic branches - exist for collaborating on features, or for code-review purposes. * Maintenance Release Branches - exist as "next" branches for maintenance releases (e.g. 2.4.1) Cordova uses tags to label releases. * Each release candidate has a tag. e.g. "2.2.0rc1" * Each release has a tag. e.g. "2.2.0" * The "latest" tag points to the last stable release (this follows npm conventions) 1. The "next" branch. * This branch is used only when in the process of doing a release. * All tags are created from this branch. * All release-candidate bug-fixes are done on this branch. 2. The "master" branch. * When not in the release-process, all commits are made here * When in the release-process, all non-bugfix commits are made here * This is where topic-branches are merged into.
