Hi everyone,

I'd like to start the community vote for Apache Fluss 1.0.0, release
candidate 3. The RC2 was cancelled because it uses a conflict version
(1.0.0) of pyfluss.

The candidate artifacts are available at the following locations:

Source and binary distributions, including Gateway binaries for Linux
amd64 and arm64:
https://dist.apache.org/repos/dist/dev/fluss/fluss-1.0.0-rc3/

Helm chart:
https://dist.apache.org/repos/dist/dev/fluss/helm-chart/1.0.0-rc3/

When testing the chart, please override the image tag with --set
image.tag=1.0.0-rc3.

Maven staging repository:
https://repository.apache.org/content/repositories/orgapachefluss-1016/

Python client (pyfluss 1.0.0rc3) on TestPyPI:
https://test.pypi.org/project/pyfluss/1.0.0rc3/

Git tag:
https://github.com/apache/fluss/releases/tag/v1.0.0-rc3

Git commit:
https://github.com/apache/fluss/commit/5c07f88e50a8ff41b0ebc214a0458e5dba60be37

Signing key fingerprint:
E2C45417BED5C104154F341085BACB5AEFAE3202

The public key is available in the KEYS file:
https://dist.apache.org/repos/dist/release/fluss/KEYS

The following Docker images are available for testing:
- apache/fluss:1.0.0-rc3
- apache/fluss-gateway:1.0.0-rc3
- apache/fluss-quickstart-flink:1.20-1.0.0-rc3

Release announcement draft:
https://github.com/apache/fluss-blog/pull/15

Download link update:
https://github.com/apache/fluss/pull/4418

Upgrade notes:
https://github.com/apache/fluss/blob/release-1.0/website/docs/maintenance/operations/upgrade-notes-1.0.md

Please try the candidate and include the checks you performed with
your vote. The verification guide covers signatures, checksums,
builds, licenses, and functional testing:
https://fluss.apache.org/community/how-to-release/verifying-a-fluss-release/

Please reply with your vote:

[ ] +1: Support releasing this candidate
[ ] -1: Oppose releasing this candidate (please explain the issues)

Voting will remain open for a minimum of 72 hours. Approval requires a
majority in favor, including at least three binding +1 votes from PMC
members. Votes and testing feedback from all community members are
welcome.

Thanks,
Jark & Keith

Reply via email to