+1 (binding)

1: Verifying signatures (ok)

2: Verifying checksums (ok)

3: Verifying build (ok)

4: Run quick-start with Paimon, everything works as expected

5: Run quick-start with Iceberg, everything works as expected

Best regards,
Yuxia

----- 原始邮件 -----
发件人: "Yuepeng Pan" <[email protected]>
收件人: "dev" <[email protected]>
发送时间: 星期二, 2025年 10 月 28日 下午 4:48:35
主题: Re:Re: [VOTE] Release Fluss 0.8.0-incubating (RC1)

+1 non-binding

Best,
Yuepeng Pan.













At 2025-10-28 15:24:32, "Jean-Baptiste Onofré" <[email protected]> wrote:
>+1 (binding)
>
>NB: the binary distribution should be fixed (see later).
>
>I checked:
>- Source distribution
>-- incubating is in the name/version
>-- signature and checksum are good
>-- DISCLAIMER is there
>-- LICENSE and NOTICE are good (NB: it would be good to mention Maven
>in LICENSE/NOTICE as we bundle mvnw in the source distribution)
>-- No binary file found in the source distribution
>-- ASF header is present in expected files and good (just missing in a
>couple of README.md, but not blocker/required)
>- Binary distribution
>-- incubating is in the name/version
>-- signature and checksum are good
>-- DISCLAIMER is missing in the source distribution
>-- LICENSE is missing in the root directory (for Fluss itself)
>-- LICENSE files in the licenses directory and NOTICE file are good
>-- ASF header is present in configuration file (in the conf folder)
>
>Thanks,
>Regards
>JB
>
>On Tue, Oct 28, 2025 at 7:17 AM Nicholas <[email protected]> wrote:
>>
>> +1 (binding).
>>
>>
>> I verified
>>
>>
>> - Download links are valid.
>> - Git commit hash is correct.
>> - Checksums and signatures are valid.
>> - DISCLAIMER, LICENSE and NOTICE exist.
>> - Successfully built the binary from the source.
>> - Runt quick start of fluss works well.
>>
>>
>> Regards,
>> Nicholas Jiang
>>
>>
>> ----- Original Message -----
>> From: "Jark Wu" <[email protected]>
>> To: dev <[email protected]>
>> Sent: Sun, 26 Oct 2025 16:01:09 +0800
>> Subject: [VOTE] Release Fluss 0.8.0-incubating (RC1)
>>
>> Hi everyone,
>>
>> Please review and vote on the release candidate #1 for the Apache Fluss
>> version 0.8.0-incubating, as follows:
>> [ ] +1, Approve the release
>> [ ] -1, Do not approve the release (please provide specific comments)
>>
>>
>> The complete staging area is available for your review, includes:
>>
>> The official source release and binary convenience releases to be deployed
>> to:
>> *
>> https://dist.apache.org/repos/dist/dev/incubator/fluss/fluss-0.8.0-incubating-rc1/
>>
>> Helm charts are available on:
>> * https://dist.apache.org/repos/dist/dev/incubator/fluss/helm-chart
>> (NB: you have to build the Docker images locally with the version
>> 0.8.0-incubating in order to test Helm charts)
>>
>> All the files are signed with the key with fingerprint 85BACB5AEFAE3202,
>> you can find the KEYS file here:
>> * https://dist.apache.org/repos/dist/release/incubator/fluss/KEYS
>>
>> All artifacts to be deployed to the Maven Central Repository:
>> * https://repository.apache.org/content/repositories/orgapachefluss-1002/
>>
>> Git tag for the release:
>> * https://github.com/apache/fluss/releases/tag/v0.8.0-incubating-rc1
>>
>> Git commit for the release:
>> *
>> https://github.com/apache/fluss/commit/c18e53ed053161699163b0a5aa67141a61ae53b6
>>
>> Website pull request for the release announcement blog post
>> * https://github.com/apache/fluss/pull/1868
>>
>> Website pull request for listing the new release on the download page
>> * https://github.com/apache/fluss/pull/1868
>>
>> Upgrade note for the new release:
>> *
>> https://github.com/apache/fluss/blob/release-0.8/website/docs/maintenance/operations/upgrade-notes-0.8.md
>>
>> Docker images for the release candidate:
>> * fluss: apache/fluss:0.8.0-incubating-rc1
>> * quickstart: apache/fluss-quickstart-flink:1.20-0.8.0-incubating-rc1
>>
>> Please download, verify and test. To learn more about how to verify:
>> https://fluss.apache.org/community/how-to-release/verifying-a-fluss-release/
>>
>>
>> The vote will be open for at least 72 hours. It is adopted by majority
>> approval, with at least 3 PPMC affirmative votes.
>>
>> Thanks,
>> Jark Wu

Reply via email to