The owner of the release needs to complete the following steps BEFORE merging the version-bump branch and tagging the release:
[ ] resolve all secret issues, private issues, or issues with the plugin that are otherwise documented outside of this public repository
[ ] resolve all GitHub maintainer security advisories: merge and publish.
[ ] update and sort the changelog
[ ] make sure changelog has all items from this release, and all PRs and issues are linked
[ ] check that ordering and grouping of items is logical.
[ ] New features list
[ ] Dev-facing updates
[ ] Bugfixes
[ ] Potentially breaking changes and upgrade notices
[ ] Which versions of PHP was this tested against? (why) List the PHP versions that we're sure of and that WordPress supports. (See https://github.com/INN/largo/issues/1801)
[ ] tweet announcement and schedule 2-5 for the next 7 days (via TweetDeck, HootSuite, or similar) with simple download prompt or tweets detailing new features, like "Newsroom Staff Pages should be clean and useful. We think so too. See Largo 0.X's new...." Make sure these tweets get cross-tweeted between INN accounts.
[ ] add to Nerd Alert for following week
[ ] create the release ticket for the next milestone from this one
[ ] prune stale and merged branches
[ ] notify maintainers of related plugins: News Project, WP AMP, Amplify
Team Prep Work
release.sh
in INN/docs and copy them into this pluginrelease.txt
Before merging
The owner of the release needs to complete the following steps BEFORE merging the version-bump branch and tagging the release:
Stable tag
Version
pym_plugin_version()
Release process
git tag -s
and push to GithubAfter release is published