voonhous commented on code in PR #19959:
URL: https://github.com/apache/hudi/pull/19959#discussion_r4023556464
##########
release/release_guide.md:
##########
@@ -312,7 +312,27 @@ Source Release step) -- otherwise the voted tarball ships
a `-SNAPSHOT` Trino pi
5. Verify the released Trino resolves from Central against an empty local
repository
(scope the check to io.trino: the module's hudi siblings are not on Central
until this release completes):
`mvn dependency:get -Dartifact=io.trino:trino-hive:NNN
-Dmaven.repo.local=$(mktemp -d)`
-6. CI and the E2E workflow then run with zero SPI drift; the staging deploy
flow in "Build a release candidate"
+6. Check for dependency drift before cutting the RC: hudi-trino compiles and
tests against Hudi's managed versions,
+ while the plugin bundles Trino's `NNN` versions. Dispatch the drift check
on the release branch. The run stays
+ green either way: drift shows as a `Dependency drift` warning and a table
in the run's job summary, and files or
+ updates the drift issue:
+ `gh workflow run hudi_trino_dependency_drift.yml -R apache/hudi --ref
release-X.Y.Z`
+ Or run it locally from the release branch (JDK 17 for the first command,
JDK 25 for the rest, with a
+ `trinodb/trino` checkout at `TAG_SHA`):
+ ```
+ mvn install -pl
:hudi-common,:hudi-hive-sync,:hudi-io,:hudi-sync-common,:hudi-client-common,:hudi-java-client
-am -Dmaven.test.skip=true -Drat.skip -Dcheckstyle.skip
+ scripts/trino/bootstrap_trino.sh /path/to/trino
Review Comment:
Added in 0e11f1191026 with the workflow wording, and the local recipe now
lists both scopes like the workflow does.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
