Closed rowanmiller closed 2 years ago
@divega that's a good point. Sorry I don't have a good solution for that, and providers are a big deal. I guess I missed the 'play nice with providers' requirement.
Undone by #2677
:+1: Thanks all for taking this into consideration
What happened? what's the final outcome then ?
It got reverted! :+1:
Hey All,
Thanks for all the feedback. We discussed this at length and ultimately decided to revert this change (thus removing the major version from the package names). While we have not been able to come up with any concrete scenarios where the major-version-in-name approach was broken, and there does seem to be value in preventing inadvertent upgrades across major version boundaries, we ultimately agreed that we shouldn't try and do anything special in EF to solve this.
BTW it is worth noting that providers may choose to still use a different package name for each EF major version (in fact some already do this for EF5/6). We will leave this decision up to individual provider writers to do what they feel is best.
~Rowan
thank @rowanmiller for the headups. Great news :+1:
Will the EntityFramework metapackage stay gone, or is that being reverted too? Also what is the timeframe for these name changes to go live on myget?
@crozone It has been removed.
Thanks for listening to the feedback!
Implement the naming principles we agreed on https://github.com/aspnet/EntityFramework/wiki/NuGet-Package-Naming