docs: Updating release checklist with Hotfix release instructions #7700
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
wtogami
reviewed
Sep 29, 2024
|
|
||
| ## Performing the Point (hotfix) Release | ||
|
|
||
| 1. Create a new branch named `release-<VERSION>.<POINT_VERSION>`. |
There was a problem hiding this comment.
I had wondered why the branches are not named like release-<VERSION>.y where commits are added to the long-lived branch over time and tags happen along that branch like v24.08.1 and v24.08.2 etc. The current point release process is confusing because release-24.08.1 existed as a branch prior to release making it unclear for those following the branch if was released or if they're running an incomplete version of the branch.
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.
Changelog-None.