+1 (non-binding)

Verified build/test. And also verified with internal builds.

Thanks Huaxin for driving this.

- Aihua

On Fri, Dec 19, 2025 at 8:38 AM Daniel Weeks <[email protected]> wrote:

> +1 (binding)
>
> Verified sigs/sums/license/build/test (Java 21)
>
> Test run wasn't fully clean due to port assignment issues in Spark
> (succeeded on retry)
>
> -Dan
>
> On Fri, Dec 19, 2025 at 7:45 AM Bryan Keller <[email protected]> wrote:
>
>> +1 (non-binding)
>>
>> We're running our internal data management system using 1.10.1-rc2 (with
>> some proprietary changes) and no problems to report.
>>
>> -Bryan
>>
>> On Dec 16, 2025, at 11:51 AM, huaxin gao <[email protected]> wrote:
>>
>> Hi Everyone,
>>
>> I propose that we release the following RC as the official Apache Iceberg
>> 1.10.1 release.
>>
>> The commit ID is ccb8bc435062171e64bc8b7e5f56e6aed9c5b934
>> * This corresponds to the tag: apache-iceberg-1.10.1-rc2
>> * https://github.com/apache/iceberg/commits/apache-iceberg-1.10.1-rc2
>> *
>> https://github.com/apache/iceberg/tree/ccb8bc435062171e64bc8b7e5f56e6aed9c5b934
>>
>> The release tarball, signature, and checksums are here:
>> *
>> https://dist.apache.org/repos/dist/dev/iceberg/apache-iceberg-1.10.1-rc2
>>
>> You can find the KEYS file here:
>> * https://downloads.apache.org/iceberg/KEYS
>>
>> Convenience binary artifacts are staged on Nexus. The Maven repository
>> URL is:
>> *
>> https://repository.apache.org/content/repositories/orgapacheiceberg-1276/
>>
>> Please download, verify, and test.
>>
>> Instructions for verifying a release can be found here:
>> * https://iceberg.apache.org/how-to-release/#how-to-verify-a-release
>>
>> Please vote in the next 72 hours.
>>
>> [ ] +1 Release this as Apache Iceberg 1.10.1
>> [ ] +0
>> [ ] -1 Do not release this because...
>>
>> Only PMC members have binding votes, but other community members are
>> encouraged to cast
>> non-binding votes. This vote will pass if there are 3 binding +1 votes
>> and more binding
>> +1 votes than -1 votes.
>>
>> Best,
>> Huaxin
>>
>>
>>

Reply via email to