Update backport template and servicing docs #83795
Merged
Conversation
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
carlossanlop
changed the title
|
Tagging subscribers to this area: @dotnet/runtime-infrastructure Issue DetailsWe are planning a small change in the backporting process: We created new staging branches for servicing releases (
|
carlossanlop
requested review from
ViktorHofer,
akoeplinger,
hoyosjs and
mmitche
ViktorHofer
approved these changes
Mar 28, 2023
ghost
locked as resolved and limited conversation to collaborators
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
We are planning a small change in the backporting process: We created new staging branches for servicing releases (
release/6.0-stagingandrelease/7.0-staging) to avoid the restriction of only merging backport PRs when the branches are open (between branding and code-complete).