+1(binding)

- verified signatures
- verified hashsums
- checked Github release tag
- built RC from source code with JDK 11
- reviewed the web PR  

Best,
Leonard

> 2026 2月 5 14:29,Gabor Somogyi <[email protected]> 写道:
> 
> +1 (non-binding)
> 
> * Downloaded all artifacts
> * Fetched sources and compiled with JDK17 + Maven 3.8.6
> * Diff of git tag checkout with downloaded sources
> * Verified SHA512 checksums & GPG certification
> * Checked that all POMs have the right expected version
> * Generated diffs to compare pom file changes with NOTICE files
> 
> BR,
> G
> 
> 
> On Wed, Feb 4, 2026 at 5:54 PM Ferenc Csaky <[email protected]> wrote:
> 
>> Hi everyone,
>> 
>> Please review and vote on release candidate #1 for flink-connector-parent
>> v2.0.0, 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, which includes:
>> * JIRA release notes [1],
>> * the official Apache source release to be deployed to dist.apache.org
>> [2], which are signed with the key with fingerprint 16AE0DDBBB2F380B [3],
>> * all artifacts to be deployed to the Maven Central Repository [4],
>> * source code tag v2.0.0-rc1 [5],
>> * website pull request listing the new release [6].
>> * CI build of the tag [7].
>> 
>> The vote will be open for at least 72 hours. It is adopted by majority
>> approval, with at least 3 PMC affirmative votes.
>> 
>> Thanks,
>> Ferenc
>> 
>> [1]
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522&version=12354451
>> [2]
>> https://dist.apache.org/repos/dist/dev/flink/flink-connector-parent-2.0.0-rc1
>> [3] https://dist.apache.org/repos/dist/release/flink/KEYS
>> [4] https://repository.apache.org/content/repositories/orgapacheflink-1887
>> [5]
>> https://github.com/apache/flink-connector-shared-utils/releases/tag/v2.0.0-rc1
>> [6] https://github.com/apache/flink-web/pull/826
>> [7]
>> https://github.com/apache/flink-connector-shared-utils/actions/runs/21679144019
>> 

Reply via email to