Hi Sergey,

+1 (non-binding)

  - verified GPG signatures for both source and binary
  - verified SHA512 checksums for both source and binary
  - no binaries found in source archive
  - source archive matches git tag release-2.1.2-rc1
  - built from source with JDK 17.0.18 and Maven 3.8.6
  - checked bytecode version is 55 (Java 11) - correct for Flink 2.x
  - verified LICENSE and NOTICE files present in source, binary, and Maven
JARs
  - checked Maven staging repository artifacts (orgapacheflink-1900)
  - started standalone cluster, run WordCountExample job, no errors in logs
  - reviewed flink-web PR

Best,

Ramin

On Sat, Apr 18, 2026 at 9:20 PM Sergey Nuyanzin <[email protected]> wrote:

> Hi everyone,
> Please review and vote on release candidate #1 for the release version
> 2.1.2, 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 F752 9FAE 2481
> 1A5C 0DF3  CA74 1596 BBF0 7268 35D8 [3],
> * all artifacts to be deployed to the Maven Central Repository [4],
> * source code tag release-2.1.2-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.
>
> [1]
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522&version=12356307
> [2] https://dist.apache.org/repos/dist/dev/flink/flink-2.1.2-rc1
> [3] https://dist.apache.org/repos/dist/release/flink/KEYS
> [4]
> https://repository.apache.org/content/repositories/orgapacheflink-1900/
> [5] https://github.com/apache/flink/releases/tag/release-2.1.2-rc1
> [6] https://github.com/apache/flink-web/pull/841
> [7] https://github.com/apache/flink/actions/runs/24603538693
>
> --
> Best regards,
> Sergey
>

Reply via email to