Release 4.0.0

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

• check integration package compatibility
  • AutoFixture.AutoFakeItEasy - @blairconrad
  • AutoFixture.AutoFakeItEasy2 - @blairconrad
  • Machine.Fakes.FakeItEasy - @blairconrad Broken. See https://github.com/FakeItEasy/FakeItEasy/issues/1117#issuecomment-317392975. Created https://github.com/machine/machine.fakes/issues/40.
  • Autofac.Extras.FakeItEasy - @thomaslevesque Works, but package downgrade warnings during restore. Should work with no issues if upgraded to NetStandard.Library 1.6.1. Consuming code that uses both Autofac.Extras.FakeItEasy and FakeItEasy 4.0.0-beta001 works fine.
  • EntityFrameworkTesting.FakeItEasy - @blairconrad
    • There’s been no update to the project since we released 3.0.0, and we haven’t changed anything to improve upon what we reported then:
      • Fails. IReturnValueConfiguration.ReturnsLazily signature changed. On the other hand, the package is restricted to >= 1.25.2 && < 2.0.0, so I don’t think we need to worry about it.
      • Related issue: https://github.com/scott-xu/EntityFramework.Testing/issues/17
• run code analysis in VS in Release mode and address all coding and style violations (send a regular PR 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)
• change “vNext” names to appropriate x.y.z version for the next:
  • GitHub Release
  • milestone
  • release checklist (this issue)
• create new GitHub artifacts for the next release:
  • create a new draft GitHub Release with name “vNext”
  • create a new milestone for the next release with name “vNext”
  • create a new issue (like this one) with name “Release vNext” for the next release, adding it to the new milestone
• create release-x.y.z branch on upstream
• perform any last-minute tasks on release-x.y.z
• submit a PR to merge the release-x.y.z branch to master (#1172)
• submit a PR to merge the release-x.y.z branch to develop, if there are any changes on release-x.y.z
• once release-x.y.z has been merged, tag master and push to upstream. This will push the nupkgs to nuget.org
• de-list pre-release or superseded buggy NuGet packages if present
• attach all nupkgs from the tagged build to the GitHub Release
• 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

[thomaslevesque]

The only feedback I saw was about the deprecation of fixture initialization, and that’s not something we’re going to rollback anyway.

So yes, I think we’re ready to plan the release. I can’t think of anything else we should add.

[blairconrad]

nuget.org finished indexing.