Largo 0.6.3 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 hasn't changed since Run theme check plugin against 0.6.2 #1677
• using WP sample data, go through the entire [theme unit tests checklist]
• 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
• 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
• run grunt build
• release announcement blog post written and saved as draft
• update all version numbers
• merge 0.5-dev into 0.5
• tag release git tag -s v0.6.3
• create release at https://github.com/INN/largo/releases
• close milestone

After release is tagged:

• 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 - largo-umbrella, inndev, other standalone instances (wisconsin, etc.)
• notify non-INN sites
• publish launch announcement blog post
• 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
• tweet announcement and schedule 2-5 for the next 7 days (TweetDeck, HootSuite) with simple download prompt or "Newsroom Staff Pages should be clean and useful. We think so too. See Largo 0.X's new....". Make sure they get cross-tweet'd between INN accounts.

[benlk]

Closing, will copy to 0.6.4.