Release wp-parsely 3.20.3

[alecgeatches]

This is an issue for tracking the next wp-parsely release (milestone: 3.20.3).

Unfortunately, the release for 3.20.2 failed to update on WordPress.org due to whitespace issues in the README. I'll be repeating the process with only the README code changes to ensure everything is updated properly this time.

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

• Merge any outstanding PRs due for this release to the target branch (usually develop).
• 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:

• 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

• 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).
• 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

• Run the "Bump wp-parsely version" GitHub Action to update the version numbers in the plugin files. Use the branch you want to release from (usually develop).
• Verify that the generated PR looks correct. You can amend it with new commits if needed.
• Merge the PR into the target branch (usually develop).

2. Merge develop into trunk

• Create a PR that merges the target branch (usually develop) into trunk, named Release wp-parsely 3.20.3.
• Merge the PR into trunk.

3. Create release and deploy to WordPress.org

• Check if the develop and trunk branches built successfully. You can check it in the GitHub Actions tab.
• Run the "Release wp-parsely" GitHub Action, on the trunk-built branch, inputting the new version number, and without selecting Dry run.
• Check the action logs for any errors. If there are any, fix them and rerun the action.
• Check the new release on the GitHub releases page and verify that it is correct.
• Verify that the release was successful by checking the WordPress.org plugin page.

After releasing

1. Communicate

• If needed, update the public documentation.
• Inform the concerned Slack channels about the new release, also preannouncing the WordPress VIP release.

2. Merge trunk back into develop

• Create a PR that merges trunk into develop, named Merge trunk into develop after the wp-parsely 3.20.3 release.
• Merge the PR into develop.

3. Manage milestones

• Close the current milestone.
• If needed, open a new milestone for the next release.

4. Release to other platforms

• Update the vip-go-mu-plugins submodule to the latest version (PR: Update wp-parsely submodule to version 3.20.3 Automattic/vip-go-mu-plugins#6377)
• Release the plugin for WordPress VIP.
• Release the plugin for WordPress.com.