Process for petitioning for or triggering or executing a backport/cherry-pick patch release? #24620
sthornington
started this conversation in
Ideas
Replies: 1 comment 5 replies
-
@sthornington The release playbook is more for Bazel release managers, for community member, please see https://bazel.build/release#release-procedure-policies. Basically anyone can mark a certain PR or issue as a potential release blocker with We are not planning a Bazel 7.x release yet, but will start a 8.0.1 release soon, I think we could include #24295. |
Beta Was this translation helpful? Give feedback.
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi folks - I wrote #24295 a few weeks ago, and I was somewhat dismayed to see that it was not included in the recent 8.0.0 release. This fix/feature is really important to us, and I’d like to get it into 8.0, if not also 7.4.
I have read https://github.com/bazelbuild/continuous-integration/blob/master/docs/release-playbook.md but the link to the Release Managers Team at the top of the doc goes to a 404 for me. I had kind-of assumed that actually executing a Bazel release was not something I myself could do, but I am absolutely willing to follow the checklist if it’s possible. If it’s not possible, and official releases are only doable by affiliated team members, is there someone whom I could petition to do one for this one little fix? It’s really very small, unlikely to need to change across all the branches (I checked when I wrote it, and actually developed it against 7.4 before submitting it on master as a PR), and it really means a lot to me to get this fixed once and for all.
Please advise!
Thank you,
Simon.
Beta Was this translation helpful? Give feedback.
All reactions