Release 4.3.0

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

• run code analysis in VS in Release mode and address all coding and style violations (send a regular pull request which must be merged before continuing)
• ensure completeness of draft release notes, including non-owner contributors, if any (move release notes forward from any pre-releases to the current release)
• run tools\prepare_release.cmd x.y.z to:
  • change “vNext” names to appropriate x.y.z version for the next GitHub Release, milestone, and release checklist (this issue)
  • create a new draft GitHub Release, milestone, and release checklist
  • create release/x.y.z branch on upstream, branching from develop
  • submit a pull request to merge the release/x.y.z branch to master
• merge the pull request, which may be done by the PR creator, unlike a regular pull request
• tag master with the new version number and push to upstream. This will cause the build server to
  • push the nupkgs to nuget.org and
  • attach all nupkgs from the tagged build to the GitHub Release.
• de-list pre-release or superseded buggy NuGet packages if present
• publish the GitHub release
• 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
• close this issue
• close the milestone for this release
• have readthedocs serve up “stable” as the default branch, not “latest” (temporarily changed for #1267)

[thomaslevesque]

Wanna release?

Sure. 4.3.0, since there’s a new feature?

[thomaslevesque]

Ah, I was wondering about this 😉