You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by da...@apache.org on 2023/10/18 18:38:08 UTC
[beam] branch users/damccorm/bom created (now 8a09e4634a9)
This is an automated email from the ASF dual-hosted git repository.
damccorm pushed a change to branch users/damccorm/bom
in repository https://gitbox.apache.org/repos/asf/beam.git
at 8a09e4634a9 Move Java Google BOM to best effort post-release task
This branch includes the following new commits:
new 8a09e4634a9 Move Java Google BOM to best effort post-release task
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
[beam] 01/01: Move Java Google BOM to best effort post-release task
Posted by da...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
damccorm pushed a commit to branch users/damccorm/bom
in repository https://gitbox.apache.org/repos/asf/beam.git
commit 8a09e4634a9682c5e31e6db17246f9f1c570b6e2
Author: Danny McCormick <da...@google.com>
AuthorDate: Wed Oct 18 14:38:02 2023 -0400
Move Java Google BOM to best effort post-release task
---
contributor-docs/release-guide.md | 45 ++++++++++++++++++++++++++++++---------
1 file changed, 35 insertions(+), 10 deletions(-)
diff --git a/contributor-docs/release-guide.md b/contributor-docs/release-guide.md
index 189bc61e15e..99ee13dfed0 100644
--- a/contributor-docs/release-guide.md
+++ b/contributor-docs/release-guide.md
@@ -261,16 +261,6 @@ for each release.
See if https://go.dev/doc/devel/release has a newer release. Update throughout
Beam. See example at https://github.com/apache/beam/pull/27900/files
-#### Update the Java BOM
-
-Google releases a BOM that pins compatible versions of their Java libraries.
-Ideally, this update happens as far in advance of the release as possible, such
-as just after a release. But if that was not done, consider doing it before
-cutting the release branch.
-
-To do so, follow instructions at
-https://github.com/apache/beam/blob/master/contributor-docs/java-dependency-upgrades.md.
-
### Cut the release branch
> **Note**
@@ -1356,6 +1346,41 @@ Also, update [the Wikipedia article on Apache Beam](https://en.wikipedia.org/wik
At the end of the release, go to the GitHub milestones page and mark the recently released version as closed.
+#### Update the Java BOM
+
+Google releases a BOM that pins compatible versions of their Java libraries.
+After the release, try updating the BOM to the latest version.
+
+To do so, create a draft PR and run test suites following the instructions at
+https://github.com/apache/beam/blob/master/contributor-docs/java-dependency-upgrades.md.
+
+If there are no test failures, request review and merge the PR as normal.
+
+If there are test failures due to the BOM upgrade, email the dev list and ask for a volunteer to take the update forward.
+It is not your responsibility to fix the BOM issues or to find a volunteer (though you are welcome to take it forward).
+If nobody volunteers, that is OK and this issue can roll forward to the next release.
+You can optionally use the following template for your email to the dev list:
+
+```
+From: Release Manager
+To: dev@beam.apache.org
+Subject: Java BOM Update X.Y.Z
+
+Hi everyone,
+
+Following the instructions in https://github.com/apache/beam/blob/master/contributor-docs/release-guide.md#post-release-tasks
+I've attempted to update the Java Google BOM and have run into test issues caused by the upgrade [1].
+Since the Java Google BOM update is best effort for a release manager, I'm handing this piece off to the community.
+If you would like to volunteer to help, you can get started by following the instructions in
+https://github.com/apache/beam/blob/master/contributor-docs/java-dependency-upgrades.md#google-cloud-related-dependency-upgrades
+otherwise this will roll over to the next release.
+
+Thanks,
+Release Manager
+
+[1] https://github.com/apache/beam/pull/123
+```
+
### Update Beam Playground
After new Beam Release is published, Beam Playground can be updated following the steps below: