Repository navigation
docs: document patch release and backport policy - #31946
Closed
coder[bot] wants to merge 1 commit into
Closed
coder[bot] wants to merge 1 commit into
coder[bot] wants to merge 1 commit into
Conversation
Collaborator
|
Closing and reopening under a human author, as required for this repository. |
4 tasks
This branch was previously deployed
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Adds a Patch releases and backports section to the Releases page. The page says mainline and stable receive "all bugfixes" but doesn't explain how patches reach each release:
mainfirst.cherry-pick/backportlabels inCONTRIBUTING.md.previewimage.Pairs with the Support page change in DOCS-1731 ("contact Coder support" link).
Needs policy owner confirmation before merge
Linear: DOCS-1732