Skip to main content

Pre-RC Checklist

Run through this before cutting a release candidate. It catches the problems that are expensive to discover mid-vote, now that a single tag releases Java, Rust, Python, and C++ together.

Access and secrets​

  • Maven Central (Apache Nexus) access for org.apache.fluss — see Release Manager Preparation
  • Trusted Publishing configured on crates.io, PyPI, and TestPyPI, each still naming apache/fluss and the right workflow file — see Release Manager Preparation
  • crates.io owner of fluss-rs; PyPI maintainer of pyfluss
  • The ASF Infra request for apache/fluss-gateway is resolved, the Docker Hub repository exists, and the release manager has access to apache/fluss, apache/fluss-gateway, and apache/fluss-quickstart-flink
  • GPG key published to the Apache KEYS file

Build and publish dry-runs​

  • the RC tag's rust-release.yml run authenticated against crates.io — that step is the only check that the Trusted Publishing config is correct before the release tag

  • cargo publish -p fluss-rs --dry-run succeeds

  • Python wheels + sdist install from TestPyPI (the RC tag publishes there):

    pip install -i https://test.pypi.org/simple/ pyfluss==${RELEASE_VERSION}

  • fluss-cpp Bazel build smoke test passes:

    cd fluss-rust/bindings/cpp && bazel build //...

  • On native amd64 and arm64 buildx nodes, the Gateway distribution and container smoke tests pass:

    GATEWAY_ARCH=<amd64-or-arm64> \
      RUN_SMOKE=true \
      docker/fluss-gateway/build.sh

Audits​

  • cargo deny check licenses passes; the Rust dependency list is regenerated and committed
  • fluss-gateway/scripts/generate_binary_license.py --check passes and the Gateway binary LICENSE / NOTICE match its runtime dependency closure
  • Java + Rust + binding + Gateway CI is green on the release branch
  • LICENSE / NOTICE cover any third-party content bundled in the source release (including under fluss-rust/)

Once these pass, proceed to Creating a Fluss Release.