Skip to content

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

Closed
linqing2004 opened this issue Oct 28, 2020 · 2 comments
Closed

When will you have 3.1.200 released? #1842

linqing2004 opened this issue Oct 28, 2020 · 2 comments
Labels
area-product-experience Improvements in the end-user's product experience area-release Release tasks or related issues

Comments

@linqing2004
Copy link

The latest 3.1.109 don't support "dotnet nuget add ...". I wonder when will you have source build for 3.1.200?

@dagood
Copy link
Member

dagood commented Oct 28, 2020

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 >= 3.1.2xx?)

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:

image

through a search engine to these support pages:
https://docs.microsoft.com/en-us/visualstudio/releases/2019/release-notes-v16.4
https://docs.microsoft.com/en-us/visualstudio/releases/2019/release-notes (v16.7 as of writing)

the 16.7 one says:

In addition, now that version 16.7 is available, version 16.4, which was the last servicing baseline, will be supported for an additional 12 months and will go out of support in October 2021.

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.

@dagood dagood added area-product-experience Improvements in the end-user's product experience area-release Release tasks or related issues labels Oct 28, 2020
@dseefeld
Copy link
Contributor

dseefeld commented Nov 5, 2020

@linqing2004 We think this question is answered. If you have any other questions or comments, please let us know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-product-experience Improvements in the end-user's product experience area-release Release tasks or related issues
Projects
None yet
Development

No branches or pull requests

3 participants