From f0bda81a49032910e243e1ea9c2922f94fc98fc1 Mon Sep 17 00:00:00 2001 From: Sutou Kouhei Date: Mon, 20 Jan 2025 10:16:00 +0900 Subject: [PATCH] GH-533: [Release] Add a post release task for publishing staged .jar Fixes GH-533. This is borrowed from ADBC: https://arrow.apache.org/adbc/current/development/releasing.html --- dev/release/README.md | 16 +++++++++++++--- 1 file changed, 13 insertions(+), 3 deletions(-) diff --git a/dev/release/README.md b/dev/release/README.md index 0294ebedc9..f62befba03 100644 --- a/dev/release/README.md +++ b/dev/release/README.md @@ -120,11 +120,12 @@ problem, we'll increment the RC number such as RC2, RC3 and so on. We need to do the followings to publish a new release: - * Publish to apache.org + * Publish the source archive to apache.org + * Publish the binary artifacts to repository.apache.org Run `dev/release/release.sh` on a working copy of -`git@github.com:apache/arrow-java` not your fork to publish to -apache.org: +`git@github.com:apache/arrow-java` not your fork to publish the source +archive to apache.org: ```console $ GH_TOKEN=${YOUR_GITHUB_TOKEN} dev/release/release.sh ${VERSION} ${RC} @@ -139,6 +140,15 @@ $ GH_TOKEN=${YOUR_GITHUB_TOKEN} dev/release/release.sh 19.0.0 1 Add the release to ASF's report database via [Apache Committee Report Helper](https://reporter.apache.org/addrelease.html?arrow). +You need to do the followings to publish the binary artifacts to +repository.apache.org: + +* Logon to the Apache repository: + https://repository.apache.org/#stagingRepositories +* Select the Arrow staging repository you created for RC: + `orgapachearrow-XXXX` +* Click the `release` button + ### Bump version for new development We should bump version in the main branch for new development after we