SolvedPomelo.EntityFrameworkCore.MySql Upgrade to 2.1.0

Overarching issue for upgrading to EF Upstream 2.1.0 including preview releases such as 2.1.0-preview1

Information

• Working branch for 2.1.0 is master
• 2.1.0 contributions should be opened as Pull Requests against this branch
• As this branch passes CI it will be merged into master and nightly builds will be published to MyGet

Current Blockers

List of issues that need to be fixed before merging f_2.1.0-spec-tests to master

• #512
• #560
• #561
• #553
• #578
• #580

2.1.0-rc1-final is released on NuGet!

A big thanks to @AndriySvyryd and the Microsoft EF team for supporting this upgrade.

As always please open issues if you have any when upgrading. We will likely be looking to do another RC in 2 weeks, then a final release after that if everything checks out.

The first 2.1.0-rc1 build is on MyGet: 2.1.0-rc1-20180603135351

Once I can validate this package on MyGet, I'll move it over to 2.1.0-rc1-final on NuGet. If you want to try out the MyGet package, follow the instructions for adding our MyGet source

Thanks to the fantastic work of @AndriySvyryd with help from @csboling and @maumar, the master branch is now tracking EF 2.1.0!

PRs for 2.1.0 should now be opened agains master

There are 2 issues with the build right now:

• #560
• #561

.NET Core and EF 2.1.0 should be landing sometime next week, our goal is to do a Release Candidate shortly after it does.

@collinbarrett honestly I would wait for Pomelo 2.1.0-rc. microsoft.aspnetcore.all and the SDK have pretty tight dependencies. We should have the RC up sometime this weekend.

Once #568 is figured out and passing CI, it should fix #561 and we can publish a RC.