Release 5.0.0-beta.1

See original GitHub issue

Address all coding and style violations detected during a Release build (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
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.
wait for NuGet package validation
de-list pre-release NuGet packages if present
publish the GitHub release
tweet, mentioning contributors, and post link as comment here for easy retweeting 😉
post tweet in Gitter
if this is not a pre-release, post a link to the GitHub Release in each issue in this milestone, with thanks to contributors
close this issue
if this is not a pre-release, close the milestone for this release

Issue Analytics

State:
Created 5 years ago
Comments:10 (10 by maintainers)

Top GitHub Comments

1reaction

thomaslevesquecommented, Dec 18, 2018

I added the analyzer meta-package to the 5.0.0-beta.1 release, since the build won’t do it for this package.

1reaction

thomaslevesquecommented, Dec 17, 2018

Sounds good to me. There haven’t been many downloads of alpha.1, but I don’t think staying longer in alpha will give us much more feedback. So let’s go beta, I think.