This is an automated email from the ASF dual-hosted git repository.

kou pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/arrow-java.git


The following commit(s) were added to refs/heads/main by this push:
     new 7580bf5e GH-533: [Release] Add a post release task for publishing 
staged .jar (#534)
7580bf5e is described below

commit 7580bf5e231ecc8c3db79345c4b2ec704e6c5d6f
Author: Sutou Kouhei <[email protected]>
AuthorDate: Mon Jan 20 11:39:29 2025 +0900

    GH-533: [Release] Add a post release task for publishing staged .jar (#534)
    
    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 0294ebed..f62befba 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
-`[email protected]:apache/arrow-java` not your fork to publish to
-apache.org:
+`[email protected]: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

Reply via email to