Release checklist for version [next]

[benlk]

Drawing from Largo's 0.7.0 release checklist issue WPBuddy/largo#1798, the SCAMP 0.3 tag checklist INN/doubleclick-for-wp#83, and other issues:

Team Prep Work

• copy this issue into this plugin's docs folder with relevant instructions for testing
• check for upstream updates to release.sh in INN/docs into this plugin
• write release announcement
  • GitHub release drafted
    • can be copied from changelog.md
    • includes encouragement to say hi if you're using the plugin. (This fulfills the "who's using our stuff?" goal in Does Largo need to do anything in response to the 4.9.6 GDPR update? WPBuddy/largo#1495)
  • labs.inn.org blog post written and saved as draft, based on changelog
  • MailChimp campaign for Largo User mailing list drafted: Plan for Largo User mailing list publicity and communication WPBuddy/largo#1796

Before merging

The owner of the release needs to complete the following steps BEFORE merging the version-bump branch and tagging the release:

• run the theme check plugin and address any outstanding issues.
• resolve all secret issues, private issues, or issues with the theme 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 Travis updates: drop PHP 7.0, add 7.2 and 7.3 WPBuddy/largo#1801)
• check that the blog post and changelog items are done
• update all version numbers. 0.7-prerelease.x all become 0.7.0.
  • readme.md
  • package.json
  • docs/conf.py
  • style.css

Release process

• bump version number
• tag and push to github
• release.sh
• publish release in GitHub
• close milestone

After release is published

• update plugins on our sites (inndev? ccs?)
• publish update announcement blog post
• 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