Skip to content

GH-533: [Release] Add a post release task for publishing staged .jar #534

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 20, 2025
Merged

GH-533: [Release] Add a post release task for publishing staged .jar #534

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 13 additions & 3 deletions dev/release/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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}
Expand All @@ -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
Expand Down
Loading