This guide is for Apache Iceberg committers and PMC members who are managing a release.
git, gh (GitHub CLI), gpg, svnYour PGP key must be published in the KEYS file. For first-time release managers:
# Check out the release distribution directory svn co https://dist.apache.org/repos/dist/release/iceberg cd iceberg # Append your GPG public key echo "" >> KEYS gpg --list-sigs <YOUR_KEY_ID> >> KEYS gpg --armor --export <YOUR_KEY_ID> >> KEYS svn commit -m "Add GPG key for <YOUR_NAME>"
Run release_rc.sh on a working copy of apache/iceberg-cpp (not your fork):
git clone git@github.com:apache/iceberg-cpp.git && cd iceberg-cpp GH_TOKEN=${YOUR_GITHUB_TOKEN} dev/release/release_rc.sh ${VERSION} ${RC}
For example, to release RC0 of version 0.3.0:
GH_TOKEN=${YOUR_GITHUB_TOKEN} dev/release/release_rc.sh 0.3.0 0
The script will:
v0.3.0-rc0)dev@iceberg.apache.orgIf an RC has problems, increment the RC number (RC1, RC2, etc.) and repeat.
After the vote passes (requires 72 hours and at least 3 binding +1 votes), publish the release:
GH_TOKEN=${YOUR_GITHUB_TOKEN} dev/release/release.sh ${VERSION} ${RC}
The script will:
v0.3.0)After running the script, add the release to ASF's report database.