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: https://wiki.apache.org/cordova/CuttingReleases?action=diff&rev1=61&rev2=62 ./cordova-coho/coho tag-release --version 2.8.0-rc1 -r android }}} - == Tagging cordova-cli == + == Tagging RC1 of cordova-cli == cordova-cli doesn't use a release branch. Follow the instructions at StepsForToolsRelease, but in addition: 1. Run [[http://creadur.apache.org/rat/ | Apache RAT]] to ensure copyright headers are present * `./cordova-coho/coho audit-license-headers -r cli | less` 1. Update the tool to point to the new repo versions (within `cordova-cli/platforms.js`) + 1. Instead of the normal `npm publish` flow: + {{{ + npm view cordova@latest dist-tags.latest > /tmp/cdvtag + npm publish . + npm tag cordova rc + npm tag cordova@$(</tmp/cdvtag) latest + rm /tmp/cdvtag + }}} == Testing & Documentation == @@ -116, +124 @@ === What to Test === - * Run [[http://git-wip-us.apache.org/repos/asf/incubator-cordova-mobile-spec.git | mobile-spec]] + * Run [[http://git-wip-us.apache.org/repos/asf/cordova-mobile-spec.git | mobile-spec]] * Don't forget to set up your white-list * Don't forget to run through the manual tests in addition to the automatic tests * Test loading the app over HTTP (via "cordova serve" and setting the config.xml start page) @@ -137, +145 @@ * `./cordova-coho/coho foreach "git checkout 2.9.0"` * `./cordova-mobile-spec/createmobilespec.sh` 2. Upgrade the project via the update command: - * `../cordova-cli/bin/cordova upgrade-project` + * `../cordova-cli/bin/cordova platform update PLATFORM` 3. Test the result: * Project should run * cordova/version should report the new version @@ -166, +174 @@ # Author Count: git log --pretty=format:'%an' --topo-order --no-merges origin/RELEASE_BRANCH..master | sort | uniq | wc -l }}} - a. Edit the commit logs - don't add the commits verbatim, usually they are meaningless to the user. Only show the ones relevant for the user (fixes, new features) + a. Edit the commit descriptions - don't add the commits verbatim, usually they are meaningless to the user. Only show the ones relevant for the user (fixes, new features) - a. Put the edited logs into a new section for the new version with a date (YYYYMMDD) in parentheses, and follow the previous formats 1. Update README.md (if necessary) 1. Ensure the [[http://docs.phonegap.com/en/edge/guide_upgrading_index.md.html | Upgrade Guide]] for your platform is up-to-date 1. Ensure the other guides listed in the sidebar are up-to-date for your platform
