2.2.0 release

Can be labelled ready when all other issues on this milestone are closed.

• run code analysis in VS in Release mode and address violations (send a regular PR which must be merged before continuing)
• if necessary, change VERSION_SUFFIX on the CI Server to appropriate “-beta123” or “” (for non-betas) value and initiate a build
• check build
• edit draft release in GitHub UI:
  • ensure completeness of release notes, including non-owner contributors, if any (move release notes forward from any pre-releases to the current release)
  • attach main nupkg and/or analyzer nupkg, whichever have content to release
  • publish the release
• push nupkg(s) to NuGet
• de-list pre-release or superseded buggy NuGet packages if present
• update website with contributors list (if in place)
• tweet, mentioning contributors and post link as comment here for easy retweeting 😉
• post tweet in Gitter
• post a link to the GitHub Release in each issue in this milestone, with thanks to contributors
• run rake next_version[new_version] to
  • create a pull request that changes the version in CommonAssemblyInfo.cs to the expected version (of form xx.yy.zz)
  • create a new draft GitHub Release
  • create a new milestone for the next release
  • create a new issue (like this one) for the next release, adding it to the new milestone
• close this milestone

[thomaslevesque]

https://twitter.com/fakeiteasyfx/status/753581763688034304

Ah, forgot to post the link… Thanks 😉

[adamralph]

I can probably take this on tomorrow.