-
Notifications
You must be signed in to change notification settings - Fork 136
When will you have 3.1.200 released? #1842
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
Comments
We won't ever build 3.1.200 because it's not a secure version, and more generally, the whole 3.1.2xx feature band of SDK versions is EOL, so we won't build e.g. 3.1.202 either. I think you really want 3.1.4xx? (An SDK feature band that's in support and Context: the latest released 3.1 SDK versions are 3.1.109 and 3.1.403--all 3.1.2xx and 3.1.3xx SDKs don't have security patches: https://dotnet.microsoft.com/download/dotnet-core/3.1. Source-build supports the oldest in-service feature band (currently 3.1.1xx) for compatibility reasons: we don't want to break our users any more than necessary. 3.1.4xx, like any new feature band, has some breaking changes. Band-to-band breaks are expected to be minor, but that's a matter of opinion and case-by-case impact. We could support source-build for multiple SDK feature bands at the same time. The problem is that it takes a significant chunk of ongoing time to maintain source-build for multiple 3.1 SDK feature bands, so we don't have a plan to do that for 3.1. (In future major releases, we aim to reduce the maintenance cost to make this feasible: #1743.) All that said, an upgrade to a new band may happen sometime down the line. Once 3.1.1xx goes EOL, we'll have switch to some other SDK feature band still in support to maintain our overall 3.1 support. I think a generally accurate way to get the EOL date is following these VS version pointers from the download page like this one: through a search engine to these support pages: the 16.7 one says:
I think at that point the 3.1.1xx band will go EOL because VS no longer needs it, and we'll need to move to 3.1.4xx. |
@linqing2004 We think this question is answered. If you have any other questions or comments, please let us know. |
The latest 3.1.109 don't support "dotnet nuget add ...". I wonder when will you have source build for 3.1.200?
The text was updated successfully, but these errors were encountered: