Dear Wiki user, You have subscribed to a wiki page or wiki category on "Cordova Wiki" for change notification.
The "StepsForPluginRelease" page has been changed by AndrewGrieve: https://wiki.apache.org/cordova/StepsForPluginRelease?action=diff&rev1=8&rev2=9 * Add a comment to the JIRA issue stating which plugins had commits - == Update Changelog & Version == + == Update RELEASENOTES.md & Version == * For each plugin that has unreleased commits: - a. Update its CHANGELOG.md file with changes + a. Update its RELEASENOTES.md file with changes a. Increase the plugin's version within plugin.xml using `SemVer` (deduce the semantic effect on version), and remove the ''-dev'' suffix. a. Commit these two changes together to the `dev` branch {{{ git log --pretty=format:'* %s' --topo-order --no-merges master..dev - # Copy & paste into CHANGELOG.md + # Copy & paste into RELEASENOTES.md # Edit version within plugin.xml based off of changes. - git commit -am "[CB-####] Updated version and changelog for release ''$VERSION''" + git commit -am "[CB-####] Updated version and RELEASENOTES.md for release ''$VERSION''" }}} @@ -59, +59 @@ * Create mobilespec using the old versions of plugins (by checking them out to the previous tag) * Perform a "plugin upgrade" for plugins that have changes * Right now, this means doing a `plugin remove` followed by a `plugin add` - * Run through mobilespec, ensuring to do manual tests that relate to changes in the changelog + * Run through mobilespec, ensuring to do manual tests that relate to changes in the RELEASENOTES.md == Prepare Blog Post == - * Combine highlights from changelogs into a Release Announcement blog post + * Combine highlights from RELEASENOTES.md into a Release Announcement blog post * Instructions on [[https://svn.apache.org/repos/asf/cordova/site/README.md|sites page README]] * Get blog post proof-read.
