+1 (binding)

Ran signatures/checksums/tests/license

Kind regards,
Fokko

Op di 27 mei 2025 om 14:48 schreef Péter Váry <peter.vary.apa...@gmail.com>:

> +1 (binding)
> tested signatures, built, run some tests
>
> Ajantha Bhat <ajanthab...@gmail.com> ezt írta (időpont: 2025. máj. 27.,
> K, 14:40):
>
>> +1 (non-binding)
>>
>> * validated checksum and signature
>> * checked license docs & ran RAT checks
>> * ran build and tests
>>
>> - Ajantha
>>
>>
>> On Tue, May 27, 2025 at 7:19 AM Yuya Ebihara <
>> yuya.ebih...@starburstdata.com> wrote:
>>
>>> +1 (non-binding)
>>>
>>> Confirmed that Trino and Starburst CI are green.
>>> It runs tests against several catalogs, including HMS, Glue, JDBC
>>> (PostgreSQL), REST (Polaris, Unity, S3 Tables, Tabular), Nessie, and
>>> Snowflake.
>>>
>>> Yuya
>>>
>>> On Sat, May 24, 2025 at 7:37 AM Steven Wu <stevenz...@gmail.com> wrote:
>>>
>>>> +1 (binding)
>>>>
>>>> Checked signature, checksum, and licenses.
>>>> "./gradlew build" passed with the source bundle.
>>>> Ran Flink 1.20 with SQL
>>>>
>>>> On Fri, May 23, 2025 at 10:42 AM Russell Spitzer <
>>>> russell.spit...@gmail.com> wrote:
>>>>
>>>>> Discussion was back here -
>>>>> https://lists.apache.org/thread/497qxkq3nfplwo27fh959zhsc2o7hkmy
>>>>>
>>>>> On Thu, May 22, 2025 at 12:09 AM Ajantha Bhat <ajanthab...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Thanks Ebihara for pointing me to the change.
>>>>>>
>>>>>> We should probably capture end user related changes in the release
>>>>>> notes (separate section).
>>>>>> I will close that issue.
>>>>>>
>>>>>> I am good with this RC. I will test and vote.
>>>>>>
>>>>>> On Thu, May 22, 2025 at 10:26 AM Yuya Ebihara <
>>>>>> yuya.ebih...@starburstdata.com> wrote:
>>>>>>
>>>>>>> Hi Ajantha,
>>>>>>>
>>>>>>> https://github.com/apache/iceberg/pull/12318 made JSON un-pretty
>>>>>>> for reduing the file size.
>>>>>>>
>>>>>>> BR,
>>>>>>> Yuya
>>>>>>>
>>>>>>> On Thu, May 22, 2025 at 1:52 PM Ajantha Bhat <ajanthab...@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi Russell,
>>>>>>>>
>>>>>>>> Just observed this change (table metadata JSON file is not
>>>>>>>> formatted anymore)
>>>>>>>> https://github.com/apache/iceberg/issues/13122
>>>>>>>>
>>>>>>>> If it is induced by 1.9.0, we should probably fix it and include it
>>>>>>>> in RC?
>>>>>>>> No functional impact.
>>>>>>>>
>>>>>>>> - Ajantha
>>>>>>>>
>>>>>>>> On Thu, May 22, 2025 at 4:49 AM Russell Spitzer <
>>>>>>>> russell.spit...@gmail.com> wrote:
>>>>>>>>
>>>>>>>>> Hi Y'all,
>>>>>>>>>
>>>>>>>>> I propose that we release the following RC as the official Apache
>>>>>>>>> Iceberg 1.9.1 release.
>>>>>>>>>
>>>>>>>>> The commit ID is f40208ae6fb2f33e578c2637d3dea1db18739f31
>>>>>>>>> * This corresponds to the tag: apache-iceberg-1.9.1-rc1
>>>>>>>>> *
>>>>>>>>> https://github.com/apache/iceberg/commits/apache-iceberg-1.9.1-rc1
>>>>>>>>> *
>>>>>>>>> https://github.com/apache/iceberg/tree/f40208ae6fb2f33e578c2637d3dea1db18739f31
>>>>>>>>>
>>>>>>>>> The release tarball, signature, and checksums are here:
>>>>>>>>> *
>>>>>>>>> https://dist.apache.org/repos/dist/dev/iceberg/apache-iceberg-1.9.1-rc1
>>>>>>>>>
>>>>>>>>> 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-1202/
>>>>>>>>>
>>>>>>>>> Please download, verify, and test.
>>>>>>>>>
>>>>>>>>> Please vote in the next 72 hours.
>>>>>>>>>
>>>>>>>>> [ ] +1 Release this as Apache Iceberg 1.9.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.
>>>>>>>>>
>>>>>>>>> ---
>>>>>>>>>
>>>>>>>>> For those watching the big change between this and RC0 was the
>>>>>>>>> reversion of code which
>>>>>>>>> caused the rest client to emit multiple Snapshot Removals Requests
>>>>>>>>> in the same MetadataUpdate.
>>>>>>>>> This restores the behavior to that of 1.8.X, 1 removal per update.
>>>>>>>>> We plan to move to the new behavior in a later release
>>>>>>>>>
>>>>>>>>

Reply via email to