Hi Muhammet, I think we should also include the LICENSE and NOTICE files in the `apache/fluss` images. However, I do not consider this a blocker, as the previous 0.9.0 and 0.9.1 images also lacked these files. I have already created an issue and PRs to address this (https://github.com/apache/fluss/issues/4426, https://github.com/apache/fluss/pull/4427), so that future images will include them.
Best, Jark On Sun, 20 Sept 2026 at 11:02, Jark Wu <[email protected]> wrote: > > +1 (binding) > > - [PASS] Built and compiled Java with Temurin 11.0.28 and Maven 3.8.6, > Rust with rustc/Cargo 1.98.1, and C++ with Bazel 9.2.0 > - [PASS] Verified the SHA-512 checksums, GPG signatures, and release tag > - [PASS] Verified the source archive contents against the release tag > - [PASS] Confirmed that no Maven staging artifacts were missing > - [PASS] Verified the staged Maven client and TestPyPI package > - [PASS] Completed the quick start and client read/write workflow > - [PASS] Completed the official Docker Compose quickstarts: > real-time-analytics-flink, lakehouse-paimon, lakehouse-iceberg, > gateway, and real-time-user-profile > - [PASS] Verified the Gateway artifacts, Docker manifests, and Helm chart > - [PASS] Checked the applicable LICENSE and NOTICE files > > Non-blocking documentation issue: > > - The real-time-user-profile quickstart may produce UV = PV because > its Faker email expression generates a much larger user population > than documented: https://github.com/apache/fluss/issues/4429 > > Best, > Jark > > On Fri, 18 Sept 2026 at 19:58, Muhammet Orazov via dev > <[email protected]> wrote: > > > > Hello all, > > > > +1 (non-binding) > > > > - Signatures: > > > > The tarball artifacts and both Helm files are signed by > > E2C45417BED5C104154F341085BACB5AEFAE3202 (Jark Wu). All .sha512 OK. > > > > - Source Release > > > > The tarball does not .github, .gitignore, .idea, website/ and any > > bundled binaries. The pom file declares 1.0.0. > > > > - Build > > > > I run `mvn clean package -DskipTests` command with JDK 11, it builds > > successfully. > > > > - Helm Chart > > > > Looks fine, packages of the source helm/, the version and appVersion > > 1.0.0, and it references apache/fluss:1.0.0-rc3. > > > > - Maven Staging > > > > I built local project against orgapachefluss-1016 and ran write/read > > cycles with it. > > > > - Test > > > > I run fluss clients against a local cluster from the binary > > distribution: Java (5000 rows through both a primary-key and a log > > table), Rust (example-table and example-upsert-lookup), and pyfluss > > 1.0.0rc3 from TestPyPI (upsert, lookup, delete, bucket scan, 500-row > > append and log scan). > > > > **Again question on LICENSE / NOTICE files in docker images**: > > > > - The `apache/fluss:1.0.0-rc3` docker image has no LICENSE or NOTICE > > under /opt/fluss > > - But `apache/fluss-gateway:1.0.0-rc3` docker image contains > > /opt/fluss/LICENSE and /opt/fluss/NOTICE files > > > > Should also the `apache/fluss:1.0.0-rc` image add LICENSE and NOTICE > > files under `/opt/fluss` ? > > > > Best, > > Muhammet Orazov
