Skip to content
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

-c STS is almost meaningless when the latest major release is an LTS (e.g. .NET 8) #418

Open
nodakai opened this issue Nov 23, 2023 · 5 comments
Labels
enhancement New feature or request question User is seeking information

Comments

@nodakai
Copy link

nodakai commented Nov 23, 2023

I believe that the -c STS option should consider both STS and LTS releases, rather than focusing exclusively on STS. Alternatively, there could be a different mode that selects the newer version between STS and LTS.

Currently, -c LTS (the default) installs SDK 8.0.100, while -c STS installs 7.0.404. It seems more practical to use -c 8.0 etc. and update the channel IDs once a year, if -c STS does not automatically choose the latest major release channel.

While the current approach might align with the distribution method of release files on Azure CDN, it's not particularly convenient for the script users.

@YuliiaKovalova
Copy link
Member

Hi @nodakai,
Thank you for reporting this issue. Let's invite other people to discuss your reasoning.

@leecow & @baronfel please share your opinion on that.
Probably we can improve documentation/review the existing script design.

@YuliiaKovalova YuliiaKovalova added the question User is seeking information label Nov 28, 2023
@leecow
Copy link
Member

leecow commented Nov 28, 2023

The desired outcome is reasonable, and I recall discussions early in .NET around STS (then 'Current') and LTS resolving to the same version every other release cycle. I don't have any objections to making the change.

@baronfel
Copy link
Member

I'm ok with that change as well - my understanding is that this is more a question of how the STS channel is documented in the help and learn.ms.com docs for this tool, plus some changes to the automated processes that the release team uses to create the redirect scheme for us. Is that correct?

@YuliiaKovalova
Copy link
Member

I'm ok with that change as well - my understanding is that this is more a question of how the STS channel is documented in the help and learn.ms.com docs for this tool, plus some changes to the automated processes that the release team uses to create the redirect scheme for us. Is that correct?

You are right. And there is always a chance to download the latest version from the specified channel - it can fill the potential gap for the option absence.

@YuliiaKovalova
Copy link
Member

@baronfel, at the same time, the next SDK version is planned to be released as STS
https://dotnet.microsoft.com/en-us/platform/support/policy/dotnet-core#cadence:~:text=.-,NET,-release%20cadence
So in a year STS -> .net 9, LTS -> .net 8
@rbhanda, do I miss anything here?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request question User is seeking information
Projects
None yet
Development

No branches or pull requests

4 participants