Minor: Refine dev/release/README.md #10129
Merged
Conversation
This file contains 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
alamb
added
documentation
github-actions
bot
removed
documentation
alamb
commented
Apr 18, 2024
|
|
||
| 1. follow normal workflow to create PR to `main` branch and wait for its approval and merges. | ||
| 2. after PR is squash merged to `main`, branch from most recent release branch (e.g. `branch-18`), cherry-pick the commit and create a PR to release branch. | ||
| 1. Find (or create) the issue for the incremental release ([example release issue]) and discuss the proposed change there with the maintainers. |
There was a problem hiding this comment.
I tried to add some examples of what a release issue and backport PR looked like so we can follow the same example in the future
andygrove
approved these changes
Apr 18, 2024
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.
Which issue does this PR close?
Related to #9904
Rationale for this change
While I was working on a maintenance release in #9904 I followed this instructions and found a few things that could be improved (like links and backporting examples)
What changes are included in this PR?
Update docs
Are these changes tested?
Are there any user-facing changes?