EOL 3.1 #4171
Merged
EOL 3.1 #4171
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
📝 Design meeting notes
|
|
@ajcvickers @jcjiang Could you review the Supported .NET implementations page to make sure my messaging is all in alignment? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
.NET 3.1 goes out of support on December 13 and .NET 5 is already out of support.
Creating this draft to discuss as a team what legacy information we may still want to keep in our docs.
I'm starting extremely aggressive and assuming that anyone reading our docs will be working with a supported version of EF Core (they had a year to upgrade), and that any references to previous versions and behaviors will just create distracting noise for anyone trying to understand the current, supported versions.
TODO