+1 (non-binding) I verified: - Signatures and SHA-512 checksums for the source, Java binary, both Gateway binaries, and Helm artifacts. - Git tag signature and commit. Source files match the tag except that CLAUDE.md is packaged as a regular file instead of a symlink. - Java binary LICENSE/NOTICE, JDK 11 startup, read/write operations, and data recovery after a clean cluster restart. - Coordinator failover, KV full scans, column-statistics filtering, and multi-table subscriptions. - Maven source build with -DskipTests; Gateway Rust 1.88 build and 192 tests passed, with 1 ignored. - Local arm64 RC3 images: Gateway smoke tests, plaintext/SASL writes, and Flink 1.20 read-back and non-primary-key UPDATE/DELETE. - Helm provenance, lint, and template rendering.
Thanks, Jark and Keith, for driving the 1.0 release! Best regards, Junbo Wang > On 20 Sep 2026, at 16:09, Zhe Wang <[email protected]> wrote: > > +1 (non-binding) > > Checks I ran against the Maven staging repository (orgapachefluss-1016), > on the filesystem plugin uber-jars: > > - Signatures: fluss-fs-s3-1.0.0.jar and fluss-fs-gs-1.0.0.jar both verify as > Good signature from E2C45417BED5C104154F341085BACB5AEFAE3202 (Jark Wu), > key imported from dist/release/fluss/KEYS. > - Checksums: md5 matches for both jars; Content-Length and `unzip -t` clean > on all four (fs-s3, fs-hdfs, fs-azure, fs-gs). > - Shaded-dependency check on the four uber-jars: each ships unshaded > com/fasterxml (jackson, 1,073 entries) and unshaded com/google (guava: > 2,102 s3 / 2,791 hdfs / 2,102 azure / 7,411 gs). fluss-fs-s3 and > fluss-fs-gs contain no org.apache.fluss.fs.shaded.* package at all. > > The last point is not a blocker for RC3 — it is the known relocation gap > already tracked for 1.1 (#3553 is on the v1.1 milestone; #4116 and #4073 > remain open against main). I'm recording it only so the state of the > artifacts I checked is on the list. > > Thanks Jark and Keith for driving this. > > Best, > Zhe Wang > > Jark Wu <[email protected]> 于2026年9月18日周五 17:28写道： > >> 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 >>
