arrow/doc.goRun dev/release/release_rc.sh on a working copy of git@github.com:apache/arrow-go not your fork:
$ git clone git@github.com:apache/arrow-go.git $ dev/release/release_rc.sh ${RC} (Send a vote email to dev@arrow.apache.org. You can use a draft shown by release_rc.sh for the email.)
Here is an example to release RC1:
$ GH_TOKEN=${YOUR_GITHUB_TOKEN} dev/release/release_rc.sh 1
The argument of release_rc.sh is the RC number. If RC1 has a problem, we'll increment the RC number such as RC2, RC3 and so on.
Requirements to run release_rc.sh:
If you don't have a PGP key, https://infra.apache.org/release-signing.html#generate may be helpful.
Your PGP key must be registered to the followings:
See the header comment of them how to add a PGP key.
Apache arrow committers can update them by Subversion client with their ASF account. e.g.:
$ svn co https://dist.apache.org/repos/dist/dev/arrow $ cd arrow $ editor KEYS $ svn ci KEYS
We need to do the followings to publish a new release:
Run dev/release/release.sh to publish to apache.org:
$ GH_TOKEN=${YOUR_GITHUB_TOKEN} dev/release/release.sh ${VERSION} ${RC}
Here is an example to release 18.0.0 RC1:
$ GH_TOKEN=${YOUR_GITHUB_TOKEN} dev/release/release.sh 18.0.0 1
Add the release to ASF's report database via Apache Committee Report Helper.
We have a script to verify a RC.
You must install the following commands to use the script:
curlgpgshasum or sha256sum/sha512sumtarYou don‘t need to install Go. If Go doesn’t exist in system, the latest Go is automatically installed only for verification.
To verify a RC, run the following command line:
$ dev/release/verify_rc.sh ${VERSION} ${RC}
Here is an example to verify the release 18.0.0 RC1:
$ dev/release/verify_rc.sh 18.0.0 1
If the verification is successful, the message RC looks good! is shown.