+1(binding) Things verified.
- Signature/checksum passed. - Full build passed. - ctest: 16/16 tests passed. - Install step passed. - After "brew install fmt", the official verify_rc.sh 0.3.0 0 run completed successfully. Thanks Steven! Yufei On Sun, Jun 7, 2026 at 11:05 PM zhuo wang <[email protected]> wrote: > +1 > > Thanks for driving this release. > > Regards, > Zhuo Wang > > On Mon, Jun 8, 2026 at 1:52 PM Junwang Zhao <[email protected]> wrote: > >> Hi Steven, >> >> On Mon, Jun 8, 2026 at 1:27 PM Steven Wu <[email protected]> wrote: >> > >> > +1 (binding) >> > >> > Verified on macOS 26 (Tahoe), arm64, Apple Clang 21: >> > >> > GPG signature: OK >> > >> > SHA-512 checksum: OK >> > >> > Source build (cmake, Release, static + shared): OK >> > >> > ctest: 16/16 passed >> > >> > cmake --install: produces expected libiceberg_bundle.{a,dylib}, >> libiceberg_data, libiceberg_rest, plus vendored Arrow/Avro >> > >> > One note for other verifiers on recent macOS: dev/release/verify_rc.sh >> failed for me out of the box because the vendored avro-cpp (SHA 11fb555…) >> pins fmt 10.2.1 in its own CMakeLists, and fmt 10.2.1's format-inl.h no >> longer compiles under Apple Clang 21 / LLVM 21 due to stricter consteval >> evaluation (errors of the form "call to consteval function … is not a >> constant expression"). >> > >> > Workaround: brew install fmt (12.1.0) before running the script — >> avro-cpp's find_package(fmt QUIET) then picks up the system fmt and skips >> the FetchContent of the broken 10.2.1. After that, the full script passes. >> >> Yeah, that's a known issue. Gang has already fixed it in avro-cpp [1], >> and we'll update our dependency once the next avro release becomes >> available. >> >> [1] https://github.com/apache/avro/pull/3788 >> >> > >> > Not a blocker for this release, but worth a follow-up — either bump the >> vendored avro-cpp pin to one that uses fmt 11+, or thread an ICEBERG_FMT_* >> override through IcebergThirdpartyToolchain.cmake so we control the fmt >> version directly. >> > >> > Thanks for driving the release! >> > >> > Steven >> > >> > >> > >> > On Sun, Jun 7, 2026 at 8:12 PM Guotao Yu <[email protected]> wrote: >> >> >> >> +1 (non-binding) >> >> >> >> I verified the RC0 artifacts, checksums/signatures, and ran the unit >> tests successfully. >> >> >> >> >> >> 2026年6月6日 20:28，Junwang Zhao <[email protected]> 写道： >> >> >> >> Hi, >> >> >> >> I would like to propose the following release candidate (RC0) of >> >> Apache Iceberg C++ 0.3.0. >> >> >> >> This release candidate is based on commit: >> >> ae29c3d4b497c26a62de47ee7659f6cf7aba60f8 [1] >> >> >> >> The source release RC0 is hosted at [2]. >> >> >> >> Please download, verify checksums and signatures, run the unit tests, >> >> and vote on the release. See [3] for how to validate a release >> candidate. >> >> >> >> The vote will be open for at least 72 hours. >> >> >> >> [ ] +1 Release this as Apache Iceberg C++ 0.3.0 >> >> [ ] +0 >> >> [ ] -1 Do not release this as Apache Iceberg C++ 0.3.0 because... >> >> >> >> [1]: >> https://github.com/apache/iceberg-cpp/tree/ae29c3d4b497c26a62de47ee7659f6cf7aba60f8 >> >> [2]: >> https://dist.apache.org/repos/dist/dev/iceberg/apache-iceberg-cpp-0.3.0-rc0 >> >> [3]: >> https://github.com/apache/iceberg-cpp/blob/main/dev/release/README.md#verify >> >> >> >> -- >> >> Regards >> >> Junwang Zhao >> >> >> >> >> >> >> -- >> Regards >> Junwang Zhao >> >
