Thanks to visit codestin.com
Credit goes to github.com

Skip to content

docs: tell how to create branches for releases #2613

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 15, 2025

Conversation

rickeylev
Copy link
Collaborator

It's easier to do patch releases when the branch is already created. Some of the bugs
fixes in recent releases we probably could have easily released as patch releases if
we already had the branch ready.

@rickeylev rickeylev requested a review from aignas as a code owner February 14, 2025 06:01
Copy link
Collaborator

@aignas aignas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1 on doing patch releases through branches.

@aignas aignas added this pull request to the merge queue Feb 15, 2025
Merged via the queue into bazel-contrib:main with commit e509b7c Feb 15, 2025
3 of 4 checks passed
@rickeylev rickeylev deleted the docs.release.branches branch February 22, 2025 22:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants