This is an issue for tracking the next wp-parsely release. This ticket is to be opened the week before the actual release, so we have enough time to complete all the related tasks.
The actual release of the plugin should be done on Mondays so we can catch the Tuesday WordPress VIP release window.
Before releasing
1. Merge all outstanding work
[x] Merge any outstanding PRs due for this release to the target branch (usually develop).
[x] Verify that all important PRs have an appropriate Changelog tag. PRs without a Changelog tag won't be added to the changelog.
2. Conduct additional testing
We've got automated testing in place and also test under our local development environment during development. For impactful releases we should also:
[x] Conduct an additional smoke test under our local development environment.
[ ] Test under a regular non-local WordPress installation.
[ ] Test under a real WordPress VIP environment.
3. Communicate
[x] Inform Parse.ly support of the upcoming release.
The following additional tasks might be needed depending on the release and its impact:
[ ] Write any needed internal documentation.
[ ] Write an internal P2 post about the release (to be posted immediately so folks are aware of the release ahead of time).
[x] Write a WordPress VIP Lobby post about the release (to be posted immediately to preannounce next week's VIP release - don't forget to get someone to proofread!).
[ ] Prepare any public documentation (to be posted after the WordPress.org release).
Release process
1. Update version numbers and changelog
[x] Run php bin/release.php $OLD_VERSION $NEW_VERSION to update version numbers, the changelog, and to push the PR to GitHub. Copy the changelog's new release text for later use.
[x] Verify that the PR code looks correct. You can amend it with new commits if needed.
[x] Merge the PR into the target branch (usually develop).
2. Merge develop into trunk
[x] Create a PR that merges the target branch (usually develop) into trunk, named Release wp-parsely x.y.z.
[x] For the release's text, use the changelog text that was posted by the bin/release.php script into the PR in step 1.
[x] Verify that you're using the appropriate name and tag (should be the version that is being released, without a leading 'v' character), and publish the release.
This is an issue for tracking the next
wp-parselyrelease. This ticket is to be opened the week before the actual release, so we have enough time to complete all the related tasks.The actual release of the plugin should be done on Mondays so we can catch the Tuesday WordPress VIP release window.
Before releasing
1. Merge all outstanding work
develop).Changelogtag. PRs without aChangelogtag won't be added to the changelog.2. Conduct additional testing We've got automated testing in place and also test under our local development environment during development. For impactful releases we should also:
3. Communicate
The following additional tasks might be needed depending on the release and its impact:
Release process
1. Update version numbers and changelog
php bin/release.php $OLD_VERSION $NEW_VERSIONto update version numbers, the changelog, and to push the PR to GitHub. Copy the changelog's new release text for later use.develop).2. Merge develop into trunk
develop) intotrunk, named Release wp-parsely x.y.z.trunk.3. Create the GitHub release
trunk.bin/release.phpscript into the PR in step 1.4. Deploy the release to wordpress.org
After releasing
1. Communicate
2. Merge trunk back into develop
trunkintodevelop, named Merge trunk into develop after the wp-parsely x.y.z release.develop.3. Manage milestones
4. Release to other platforms
vip-go-mu-pluginssubmodule to the latest version.