Release checklist for tagging version 1.3.2.3

[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, Automattic/republication-tracker-tool#63, 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
• identify non-Github documentation for this plugin
  • note the location of that documentation
• update outside documentation for this plugin
  • https://support.inn.org/article/100-pym-shortcode -> Update support.inn.org docs #69
  • any other known doc

Before merging

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 Travis updates: drop PHP 7.0, add 7.2 and 7.3 WPBuddy/largo#1801)
• update description
  • in readme.txt
  • in plugin description comment
• bump version number
  • in readme.txt
  • in pym-shortcode.php
  • in readme.md
  • in docs/maintainer-notes.md
• testing as described in https://github.com/INN/pym-shortcode/blob/master/docs/maintainer-notes.md

Release process

• bump version number
• tag and push to github
• release.sh
• publish release in GitHub -> https://github.com/INN/pym-shortcode/releases/tag/v1.3.2.3
• 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 -> Release checklist for tagging version 1.3.2.4 #71
• prune stale and merged branches
• notify maintainers of related plugins: News Project, WP AMP

[benlk]

Testing without AMP:

Plugin settings:

• Does the plugin settings page work?

Shortcode tests:

• [pym src="https://blog.apps.npr.org/pym.js/examples/table/child.html"]
• [pym src="https://blog.apps.npr.org/pym.js/examples/table/child.html" pymsrc="https://pym.nprapps.org/pym.v1.min.js"]
• [pym src="https://blog.apps.npr.org/pym.js/examples/table/child.html" pymoptions=" xdomain: '\\*\.npr\.org' "]
• [pym src="https://blog.apps.npr.org/pym.js/examples/table/child.html" class="one two three four float-left mw_50"]
• [pym src="https://blog.apps.npr.org/pym.js/examples/table/child.html" align=""]
• [pym src="https://blog.apps.npr.org/pym.js/examples/table/child.html" align="none"]
• [pym src="https://blog.apps.npr.org/pym.js/examples/table/child.html" align="left"]
• [pym src="https://blog.apps.npr.org/pym.js/examples/table/child.html" align="center"]
• [pym src="https://blog.apps.npr.org/pym.js/examples/table/child.html" align="right"]
• [pym src="https://blog.apps.npr.org/pym.js/examples/table/child.html" align="wide"]
• [pym src="https://blog.apps.npr.org/pym.js/examples/table/child.html" align="full"]
• [pym src="https://blog.apps.npr.org/pym.js/examples/table/child.html" id="extremely_specific_id"]
• [pym src="https://blog.apps.npr.org/pym.js/examples/table/child.html" pymsrc="https://pym.nprapps.org/pym.v1.min.js" pymoptions="xdomain: '\\*\.npr\.org'"]
• [pym src="https://blog.apps.npr.org/pym.js/examples/table/child.html" pymsrc="https://pym.nprapps.org/pym.v1.min.js" pymoptions=""]

Gutenberg tests:

• the block, when inserted, prompts users for a URL
• the block's alignment, custom classes, custom ID, and other options are respected.
• the block uses the default pymsrc URL if the pymsrc attribute is not set
• on a site with Gutenberg not installed, the plugin functions
• on a 4.9 site with Gutenberg installed, the plugin functions
• on a 5.0 site, the plugin functions

[benlk]

AMP testing was sufficiently covered during #62, so I'm skipping that for this issue.