Release checklist

We should figure out a checklist for release so that we don't miss key bugs, cover our asses, and don't forget about our awesome partners like @jdorfman.

Rough first pass just to get things going:

• Close ship list issue (e.g., #10050 (closed))
• Open new release issue
  • Include this checklist
  • Ping folks to coordinate release (mainly @jdorfman for CDN)
• Bump version numbers in repo
  • package.json
  • bower.json
  • _config.yml
  • Use grunt change-version-number --oldver=A.B.C --newver=X.Y.Z and stage the changes manually
• Run grunt one last time
• Push to master
• git co gh-pages and git merge master
• Generate bootstrap-*.*.*-dist.zip file for release
• Cut and push release on GitHub with dist folder and release notes
• Push gh-pages
• Push blog post
• Tweet tweet

Curious if we should get more fine grained than that.

/cc @twbs/team