-
Notifications
You must be signed in to change notification settings - Fork 583
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Shall we deprecate netcoreapp3.1 build? #1984
Comments
netcoreapp 3.1 goes out of support very soon (December 13th) so I think it is totally fine to drop that asset from our packages and instead just have the new LTS version (net6.0) which we already target. That said, I think dropping a TFM support from the packages should be considered a breaking change that is only done when bumping the major version. I don't see why we can't do it now, but just wanted to mention that this should be planned for 3.0 whenever we are ready to ship that. |
I agree to that. But since we intend to do that 3.0 step anyway after the |
+1, next time we should discuss what exactly we want to plan for 3.0, which should happen quite soon. |
Go for it, fully aligned! |
I was attempting to upgrade a few dependencies (like
Microsoft.Extensions.Logging
) to V7.0.0, but this causes a lot of warnings of the formWe can either:
Since we would likely keep netstandard2.0 support, I would suggest the third option. I can't think of a reason why one would create a new project with net3.1, and projects still under development should be easy to upgrade.
The text was updated successfully, but these errors were encountered: