From b3002b9e645bf791a0b0bb32f85a317c781df21a Mon Sep 17 00:00:00 2001 From: keertk Date: Wed, 24 Jan 2024 09:36:39 -0800 Subject: [PATCH 1/3] Update comms --- docs/release-playbook.md | 10 +++------- 1 file changed, 3 insertions(+), 7 deletions(-) diff --git a/docs/release-playbook.md b/docs/release-playbook.md index b7ce61d68d..7a4384cca1 100644 --- a/docs/release-playbook.md +++ b/docs/release-playbook.md @@ -133,11 +133,9 @@ While the release is active, you should make sure to do the following: ``` Bazel 7.0.1rc1 is now available for those that want to try it out. - You can download it from here: - - https://releases.bazel.build/7.0.1/rc1/index.html - - https://github.com/bazelbuild/bazel/releases/tag/7.0.1rc1 + You can download it from here: https://github.com/bazelbuild/bazel/releases/tag/7.0.1rc1 - If you're using Bazelisk, you can point to the latest RC by setting USE_BAZEL_VERSION=last_rc. + If you're using Bazelisk, you can point to the latest RC by setting USE_BAZEL_VERSION=7.0.1rc1. Please test it out and report any issues [here](https://github.com/bazelbuild/bazel/issues) as soon as possible. A draft of the release notes can be found [here](https://docs.google.com/document/d/1pu2ARPweOCTxPsRR8snoDtkC9R51XWRyBXeiC6Ql5so/edit?usp=sharing). @@ -264,9 +262,7 @@ Note: the above policies are for final releases only. RCs can be created without * Subject: Bazel 6.2.0 is released * Body: ``` - Bazel 6.2.0 is now available: - - https://github.com/bazelbuild/bazel/releases/tag/6.2.0 - - https://releases.bazel.build/6.2.0/release/index.html + Bazel 6.2.0 is now available: https://github.com/bazelbuild/bazel/releases/tag/6.2.0 ``` 1. Post on the #general channel on the [Bazel Slack](https://bazelbuild.slack.com/) about the new release (same content as above). From 2532a932d62fe8ac123262edbeb66f2597a7de04 Mon Sep 17 00:00:00 2001 From: keertk Date: Wed, 24 Jan 2024 09:39:58 -0800 Subject: [PATCH 2/3] Edit wording --- docs/release-playbook.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/release-playbook.md b/docs/release-playbook.md index 7a4384cca1..48b12c338d 100644 --- a/docs/release-playbook.md +++ b/docs/release-playbook.md @@ -135,7 +135,7 @@ While the release is active, you should make sure to do the following: You can download it from here: https://github.com/bazelbuild/bazel/releases/tag/7.0.1rc1 - If you're using Bazelisk, you can point to the latest RC by setting USE_BAZEL_VERSION=7.0.1rc1. + If you're using Bazelisk, you can point to this RC by setting USE_BAZEL_VERSION=7.0.1rc1. Please test it out and report any issues [here](https://github.com/bazelbuild/bazel/issues) as soon as possible. A draft of the release notes can be found [here](https://docs.google.com/document/d/1pu2ARPweOCTxPsRR8snoDtkC9R51XWRyBXeiC6Ql5so/edit?usp=sharing). From a51521fe350b2fcc5fc20c0e4e24f98c5d30182b Mon Sep 17 00:00:00 2001 From: keertk Date: Wed, 24 Jan 2024 14:22:23 -0800 Subject: [PATCH 3/3] Add step --- docs/release-playbook.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/docs/release-playbook.md b/docs/release-playbook.md index 48b12c338d..fa04441159 100644 --- a/docs/release-playbook.md +++ b/docs/release-playbook.md @@ -145,6 +145,19 @@ While the release is active, you should make sure to do the following: 1. Post on the #general channel on the [Bazel Slack](https://bazelbuild.slack.com/) announcing that a new RC is out. See [example](https://bazelbuild.slack.com/archives/CA31HN1T3/p1705095377557259). +1. Post a comment on all issues / PRs addressed in this RC to ask users to test (this is a manual step for now but will eventually be automated). + + Issues: + ``` + A fix for this issue has been included in [Bazel 7.0.2 RC1](https://github.com/bazelbuild/bazel/releases/tag/7.0.2rc1). Please test out the release candidate and report any issues as soon as possible. + If you're using Bazelisk, you can point to the latest RC by setting USE_BAZEL_VERSION=7.0.2rc1. Thanks! + ``` + PRs: + ``` + The changes in this PR have been included in [Bazel 6.5.0 RC2](https://github.com/bazelbuild/bazel/releases/tag/6.5.0rc2). Please test out the release candidate and report any issues as soon as possible. + If you're using Bazelisk, you can point to the latest RC by setting USE_BAZEL_VERSION=6.5.0rc2. Thanks! + ``` + 1. Trigger a new pipeline in BuildKite to test the release candidate with all the downstream projects. * Go to https://buildkite.com/bazel/bazel-with-downstream-projects-bazel * Click "New Build", then fill in the fields like this: