Update release.md
Blog posts only for major releases + other minor fixes
Closes
@@ -17,9 +17,9 @@ assignees:
To report a release-blocking bug, please add a comment with the text `@bazel-io flag` to the issue. A release manager will triage it and add it to the milestone.
-To cherry-pick a mainline commit into X.Y, simply send a PR against the `release-X.Y.0` branch.
+To cherry-pick a mainline commit into X.Y.Z, simply send a PR against the `release-X.Y.Z` branch.
-Task list:
+**Task list:**
<!-- The first three items are only needed for major releases (X.0.0) -->
@@ -27,8 +27,8 @@ Task list:
- [ ] Create release candidate: X.Y.Zrc1
- [ ] Check downstream projects
- [ ] Create [draft release announcement](https://docs.google.com/document/d/1pu2ARPweOCTxPsRR8snoDtkC9R51XWRyBXeiC6Ql5so/edit) <!-- Note that there should be a new Bazel Release Announcement document for every major release. For minor and patch releases, use the latest open doc. -->
-- [ ] Send the release announcement PR for review: [link to bazel-blog PR]
+- [ ] Send the release announcement PR for review: [link to bazel-blog PR] <!-- Only for major releases. -->
- [ ] Push the release and notify package maintainers: [link to comment notifying package maintainers]
- [ ] Update the documentation
-- [ ] Push the blog post: [link to blog post]
+- [ ] Push the blog post: [link to blog post] <!-- Only for major releases. -->
- [ ] Update the [release page](https://github.com/bazelbuild/bazel/releases/)
