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

Documentation for OS version in TFMs should have the "earliest supported OS version" #40988

Closed
Youssef1313 opened this issue May 17, 2024 · 1 comment · Fixed by #45657
Closed
Assignees
Labels
dotnet/svc 📌 seQUESTered Identifies that an issue has been imported into Quest. standard-library/subsvc

Comments

@Youssef1313
Copy link
Member

Youssef1313 commented May 17, 2024

Type of issue

Missing information

Description

See details in dotnet/sdk#30103 (comment)

Starting with .NET SDK 9 Preview 3, the earliest bindings are supported.

For example, net8.0-ios17.0 will remain supported, regardless of whether new versions are released

So, it would be good to list the versions for every platform and for every TFM (and document that this works only with .NET 9 SDK Preview 3 and later)

Also, as the "earliest supported version" can change between previews and stable if I understand correctly, but once it's in stable, it won't change. So that would be good to note.

So, an extra column is needed in the table, which will be "earliest supported version". Then, in times of previews, there should be a note between parentheses that this version will change in stable SDK.

cc @rolfbjarne in case I got any info wrong.

Page URL

https://learn.microsoft.com/en-us/dotnet/standard/frameworks

Content source URL

https://github.com/dotnet/docs/blob/main/docs/standard/frameworks.md

Document Version Independent Id

4352856b-5ccf-8e62-48b4-3151340cac56

Article author

@gewarren

Metadata

  • ID: 49205137-dcec-a120-e5e7-1b9c79cdafbb
  • Service: dotnet
  • Sub-service: standard-library

Associated WorkItem - 417514

@rolfbjarne
Copy link
Member

So, it would be good to list the versions for every platform and for every TFM (and document that this works only with .NET 9 SDK Preview 3 and later)

If everything goes as planned, it will also work in a future service update to .NET 8.

In fact I'd hold off on changing anything until this change has been released to stable.

@BillWagner BillWagner removed the Pri1 label Jan 22, 2025
@gewarren gewarren self-assigned this Apr 4, 2025
@dotnetrepoman dotnetrepoman bot added the 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. label Apr 4, 2025
@gewarren gewarren added 🗺️ reQUEST Triggers an issue to be imported into Quest. and removed 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. labels Apr 4, 2025
@dotnet-policy-service dotnet-policy-service bot removed the ⌚ Not Triaged Not triaged label Apr 4, 2025
@sequestor sequestor bot added 📌 seQUESTered Identifies that an issue has been imported into Quest. and removed 🗺️ reQUEST Triggers an issue to be imported into Quest. labels Apr 4, 2025
@gewarren gewarren moved this from 🔖 Ready to 🏗 In progress in dotnet/docs April 2025 sprint project Apr 7, 2025
@dotnetrepoman dotnetrepoman bot added the 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. label Apr 7, 2025
@dotnet-policy-service dotnet-policy-service bot removed the 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. label Apr 7, 2025
@dotnetrepoman dotnetrepoman bot added the 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. label Apr 8, 2025
@gewarren gewarren moved this from 🏗 In progress to 👀 In review in dotnet/docs April 2025 sprint project Apr 8, 2025
@dotnet-policy-service dotnet-policy-service bot removed the 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. label Apr 8, 2025
@github-project-automation github-project-automation bot moved this from 👀 In review to ✅ Done in dotnet/docs April 2025 sprint project Apr 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dotnet/svc 📌 seQUESTered Identifies that an issue has been imported into Quest. standard-library/subsvc
Projects
Development

Successfully merging a pull request may close this issue.

5 participants