Dear Wiki user, You have subscribed to a wiki page or wiki category on "Cordova Wiki" for change notification.
The "CuttingReleases" page has been changed by AndrewGrieve: http://wiki.apache.org/cordova/CuttingReleases?action=diff&rev1=20&rev2=21 |- .md5 .................................. md5 file containing the MD5 Checksum of the src zip |- .sha .................................. sha file containing the SHA Hash of the src zip |- .asc .................................. asc file that contains the ASCII Armoring of the zip - - }}} @@ -71, +69 @@ We have recently, in the past year or so, started tagging Release Candidates about a week before the expected ship for minor release (such as 1.5.0rc1) which tends to tease out more bugs and avoid the embarrassing patch release. (1.4.1 comes to mind.) + === Tagging === - Example git flow to create a tag: + Creating the first release candidate tag of a release: {{{ - git fetch cordova # Fetch tags - git tag 2.2.0rc1 # Tag locally + git checkout next + git pull cordova next + git merge --ff-only master # Do this merge only for the first RC of a release. + git tag 2.2.0rc1 # Tag locally on the ''next'' branch + git push cordova next --tag # Push tags + }}} + + Tagging subsequent release-candidate tags: + {{{ + git checkout next + git pull cordova next + git tag 2.2.0rc2 git push cordova master --tag # Push tags }}} When going through the tagging process, sometimes bugs are found and fixed before the release candidate is even created. In this case, it's fine to change the tags via: {{{ - git fetch cordova # Fetch tags + git checkout next + git pull cordova next git tag --force 2.2.0rc1 # Re-tag locally - git push cordova master --tag # Push tags + git push cordova next --tag # Push tags }}} Once a release is created though (meaning a .zip file has been uploaded), tags should not be changed. @@ -97, +107 @@ jake git commit -am 'Tagging x.x.x' git tag x.x.x - git push --tags apache master + git push --tags apache next }}} Every time you run {{{jake}}}, it grabs the version from the VERSION file and updates any JavaScript files that require the version string appropriately. See the Jakefile for more information on this.
