Largo 0.6.4 release checklist

[benlk]

This is copied from #809, which is the reference issue for the pre-release checklist.

The owner of the release needs to complete the following steps BEFORE merging to master and tagging the release:

• run the theme check plugin and address any outstanding issues.
• using WP sample data, go through the entire theme unit tests checklist
• Update the INN Sandbox repo submodules https://github.com/INN/umbrella-innsandbox/tree/master/wp-content/themes and take a look around the sandbox sites, making sure to test all testable items. — INN/umbrella-innsandbox@a868c0c
• design checklist tktk (add to the list of theme unit tests, including style guidance, patterns that need to be followed, etc., eventually this will be codified in the INN/Largo style guide)
  • click around: don't just visually check the homepage, but also internal pages: https://github.com/INN/docs/blob/master/checklists/child-themes.md
  • Homepage /
    • Blog
    • Big Story, full-width image
    • Big story, list of featured stories
    • Big Story, list of stories from same series
    • Top Stories
    • Legacy Three Column
  • Articles /?p=1234
  • Series /series/slug/ /?series=1234
  • Category archive pages /category/slug/
  • Series archive pages /series/slug/
  • Series landing pages /slug/
  • Search results /?s=words
  • Pages /slug/
  • Tag archives /tag/slug
  • Load More Posts
  • Sticky nav
    • Mobile
    • Desktop
  • Non-sticky nav
  • Widgets
    • Default background
    • Reverse Background
    • No Background
  • Article
    • Social buttons
    • Type
    • Fonts rendered are fonts specified in stylesheet ( In Chrome: "Inspect element" on a <p>, then look at the bottom of the "Computed" tab. )
    • Image display
    • slideshows, see Navis Slideshow JS is broken from recent changes in Gutenberg; styles are misapplied #1664
  • Footer
• check that the LESS Customizer works
• test the plugins described in docs/developers/plugin-compat.rst
• move any outstanding issues to future milestones or backlog
• resolve all secret issues, private issues, or issues with the theme that are otherwise documented outside of this public repository
• update the changelog
  • New features list
  • bugfixes
  • potentially breaking changes and upgrade notices
• release announcement
  • labs.inn.org blog post written and saved as draft
  • GitHub release drafted
    • includes encouragement to say hi if you're using the theme. (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? #1495)
    • includes links to upgrade info from Find & update documentation for sites who want to upgrade the theme themselves, and make sure it's posted in our support documentation.  #1713
• update all version numbers. 0.6.4-prerelease.x all become 0.6.4.
• run grunt build
• merge 0.5-dev into 0.5

Releasing:

• tag release git tag -s v0.6.4
• create release at https://github.com/INN/largo/releases
• close milestone

After release is tagged:

• update version number on largo.inn.org, like in Bump the Largo version number to 0.5.5.4 in all references on largo.inn.org INN/umbrella-inndev#36
• bump version number in active-development branch to 0.7.0-prerelease, as described in Post-0.6.3, bump version number to 0.6.4-prerelease #1705
• rename branches as described in Clean up branch names #1571
  Post-0.6.3, bump version number to 0.6.4-prerelease #1705
• notify non-INN sites
• recompile LESS on all child themes, and see https://github.com/INN/docs/blob/master/checklists/child-themes.md
• new release needs to be deployed to our sites
  • inndev
  • innsandbox
  • inndevlearn
• compare this ticket to the template used to create this ticket, and update the template
• create the 0.6.5 release ticket from the template used to create this issue
• publish launch announcement blog post
• tweet announcement and schedule 2-5 for the next 7 days (TweetDeck, HootSuite) 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.

[benlk]

We will also need to update the helpdesk docs for the changes introduced in #1733.

[benlk]

• can we get the "you aren't reading the latest version" prompt on https://largo.readthedocs.io/ to go away?

[benlk]

Today's combined list:

• can we get the "you aren't reading the latest version" prompt on https://largo.readthedocs.io/ to go away? — @benlk
• release announcement — @kaylima
  • labs.inn.org blog post written and saved as draft
  • GitHub release drafted
    • includes encouragement to say hi if you're using the theme. (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? #1495) — @benlk
    • includes links to upgrade info from Find & update documentation for sites who want to upgrade the theme themselves, and make sure it's posted in our support documentation.  #1713 — @benlk
• rename branches as described in Clean up branch names #1571 @joshdarby
  Post-0.6.3, bump version number to 0.6.4-prerelease #1705
• notify non-INN sites
• recompile LESS on all child themes, and see https://github.com/INN/docs/blob/master/checklists/child-themes.md
• new release needs to be deployed to our sites @joshdarby
  • inndev
  • innsandbox
  • inndevlearn
• compare this ticket to the template used to create this ticket, and update the template — @benlk
• create the 0.7.0 release ticket from the template used to create this issue — @benlk
• publish launch announcement blog post
• tweet announcement and schedule 2-5 for the next 7 days (TweetDeck, HootSuite) 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.