release-process.md

Release Process

These instructions are for project maintainers wishing to create public releases of Ballista.

• Create a release-0.4 branch or merge latest from main into an existing release-0.4 branch.
• Update version numbers using ./dev/bump-version.sh
• Run integration tests with ./dev/integration-tests.sh
• Push changes
• Create v0.4.x release tag from the release-0.4 branch
• Publish Docker images
• Publish crate if possible (if we're using a published version of Arrow)

Publishing Java artifacts to Maven Central

The JVM artifacts are published to Maven central by uploading to sonatype. You will need to set the environment variables SONATYPE_USERNAME and SONATYPE_PASSWORD to the correct values for your account and you will also need verified GPG keys available for signing the artifacts (instructions tbd).

Run the follow commands to publish the artifacts to a sonatype staging repository.

./dev/publish-jvm.sh

Publishing Rust Artifacts

Run the following script to publish the Rust crate to crates.io.

./dev/publish-rust.sh

Publishing Docker Images

Run the following script to publish the executor Docker images to Docker Hub.

./dev/publish-docker-images.sh

GPG Notes

Refer to this article for instructions on setting up GPG keys. Some useful commands are:

gpg --full-generate-key
gpg --export-secret-keys > ~/.gnupg/secring.gpg
gpg --key-server keys.openpgp.org --send-keys KEYID