Add dotnetup Version Intent & Timeline Doc#55390
Open
nagilson wants to merge 15 commits into
Open
Conversation
This is very much a draft and includes my own perspectives, it will evolve and mature before it is committed. Do not consume it as official `dotnet` policy at this time. The primary intent for this document is to start conversations about the official support policy, and then to create clarity around support and the potential for breaking changes amongst our customers who have started to try-out `dotnetup` off our internal `ci` branches. Please see dotnet#54735 for more details about specific release plans and a release strategy. We have not yet consulted with the release team on this particular doc.
|
Azure Pipelines: Successfully started running 2 pipeline(s). 1 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
nagilson
commented
Jul 20, 2026
This needs to be discussed broadly before it's a commitment.
…/nagilson/sdk into nagilson-dotnetup-support-policy
…t preview policy docs state
…g doc We don't actually own those decisions on support policies and can't make them. The true intent here is to outline what the intent of each version is for us as developers (understanding when we can make a breaking change and when to document it) + communicate that outward.
nagilson
changed the title
dotnetup support policy docdotnetup Version Intent Doc
nagilson
changed the title
dotnetup Version Intent Docdotnetup Version Intent & Timeline Doc
nagilson
marked this pull request as ready for review
July 22, 2026 21:32
|
Azure Pipelines: Successfully started running 2 pipeline(s). 1 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a new internal-facing documentation page under documentation/general/dotnetup/ to describe the intent and (non-official) support expectations for dotnetup build qualities/channels, to help developers/customers choose between daily, preview, and stable.
Changes:
- Introduces a
dotnetupversion/channel intent + support-lifecycle overview document. - Documents intended platform/shell support scope and servicing expectations.
- Adds an FAQ note on how to install
stableonce available viaget-dotnetupscripts.
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
…ixes Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This document is meant to initiate conversations.
When polished, the document's function is to inform developers & customers using
dotnetupwhat the intent will be of eachdotnetupversion, and the level of support it will receive (in terms of breaking change notices, bug fixes, and security updates.)It is not an official support policy document. Such a document would be owned and persist on the https://dotnet.microsoft.com/en-us/platform/support/policy policy page. It contains my words which cannot and should not be defined as an official statement from Microsoft.
Please see #54735 for more details about specific release plans and a release strategy.