+1 (binding)

I verified the RC10 candidate with the following results:

- The source tag and release artifacts are consistent.
- SHA-512 checksums and PGP signatures are valid.
- The source archive has a single top-level directory.
- The top-level site/ directory is excluded, while docs/ is retained.
- LICENSE, NOTICE, and DISCLAIMER are present, and the Amoro NOTICE
  copyright year is 2024-2026.
- Apache RAT check passed.
- Maven validation passed.
- The project builds successfully from the source artifact with JDK 11, 17.
- The dashboard build passed.
- The Helm chart unit tests passed: 87 tests in 8 suites.
- The shaded Spark runtime JARs contain the corrected Amoro NOTICE.

I also noticed two follow-up items:

1. The frontend third-party license files under amoro-web/licenses are not
   propagated into the binary distribution. The binary licensing metadata
   should be reviewed and improved for the next candidate/release.
2. Pushing an RC tag currently publishes images to the public Docker Hub
   repository and overwrites apache/amoro:latest. The Docker publishing
   workflow should exclude release-candidate tags.

I do not consider these issues blocking for my vote, but I recommend
tracking
and addressing them promptly.

Best,
Xu Bai

ConradJam <[email protected]> 于2026年9月16日周三 16:06写道:

> Hello Amoro community,
>
> This is the tenth release candidate for Apache Amoro (incubating)
> 0.9.0-incubating.
>
> This vote supersedes and cancels the RC8 vote opened on Sep 9, which
> received no votes. It also supersedes the RC9 candidate, which I retired
> before opening its vote after Jiwon Park reported a pre-vote blocker
> (#4375): with Iceberg 1.8.1, writers could omit the next-row-id property
> when committing to V3 format-version tables, making those tables
> unreadable by Iceberg 1.9+ readers. The fix (#4376) is included in this
> RC.
>
> Changes since RC8:
>
> * [AMORO-4375][Iceberg] Prevent automatic changes to unsupported V3
>   tables (#4376)
> * [AMORO-4350][catalog] Fix Hive view handling in table management
>   (#4351)
> * [AMORO-4368][Dashboard] Fix Tables menu navigation after viewing Hive
>   tables (#4369)
> * [AMORO-4353] Set standby node state to FOLLOWER after base services
>   start (#4371)
> * [AMORO-4357][Docs] Document the table. prefix requirement for
>   catalog-level table properties (#4358)
> * [Hotfix] Remove NOTICE/LICENSE filter from shade filters (#4370)
> * [web-console][dependency] Upgrade frontend to Vue 3.5 and Vite 8
>   toolchain, lazy-load monaco (#4340)
> * [hotfix][Metrics] Iterate a locked table-runtime snapshot in gauges
>   (#4326)
> * [AMORO-4359][AMS] Support AWS Secrets Manager as a ConfigShade (#4360)
>
> The RC tag is v0.9.0-rc10, cut from master.
>
> Release artifacts:
>
> https://dist.apache.org/repos/dist/dev/incubator/amoro/0.9.0-incubating-RC10/
>
> KEYS:
> https://downloads.apache.org/incubator/amoro/KEYS
>
> Maven staging repository:
> https://repository.apache.org/content/repositories/orgapacheamoro-1087/
>
> Git tag:
> https://github.com/apache/amoro/tree/v0.9.0-rc10
>
> Website:
> https://amoro.apache.org/
>
> ====================================== VOTE
> ======================================
>
> This vote will be open for at least 72 hours and passes if at least
> three Amoro PPMC members vote +1 and no binding -1 is cast.
>
> [ ] +1 Release this package as Apache Amoro (incubating) 0.9.0-incubating
> [ ] +0
> [ ] -1 Do not release this package (please explain why)
>
> =========================== HOW TO VERIFY THE RELEASE
> ===========================
>
> * Check the download links above are valid.
> * Verify checksums and signatures of the artifacts against the KEYS
>   file; all artifacts are signed with PGP key 84027FCC19B0D30B
>   (Apache ID: czy006).
> * Check LICENSE, NOTICE, and DISCLAIMER are present, and that the
>   source release contains no unexpected binaries.
> * Check all source files have Apache license headers.
> * Build the project from source: mvn clean package -DskipTests
>   (JDK 11).
> * Spot-check the Maven staging repository for the expected artifacts.
>
> Thanks,
> czy006 (Conrad Jam)
>

Reply via email to