Hi,

+1 (non-binding)

- Verified signatures and checksums
- Verified that no binaries can be found in the source
- Built on Temurin-17.0.11+9 and Maven 3.8.6
- Started local standalone cluster and executed an example job

Best regards,
Mate

On Fri, Oct 17, 2025 at 5:10 PM Gabor Somogyi <[email protected]>
wrote:

> +1 (non-binding)
>
> - verified checksums and signatures
> - built from source with JDK17 + Maven 3.8.6
> - checked staging artifacts
> - checked git tag and the corresponding CI run
> - reviewed web PR
> - ran a simple workload which looks good
>
> BR,
> G
>
>
> On Fri, Oct 17, 2025 at 9:28 AM Zakelly Lan <[email protected]> wrote:
>
> > Hi everyone,
> >
> > Please review and vote on the release candidate #1 for the version 2.0.1,
> > 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 and binary convenience releases to
> be
> > deployed to dist.apache.org [2], which are signed with the key with
> > fingerprint E60A9680590FF0FF13B9DE01224C2311410823C4 [3],
> > * all artifacts to be deployed to the Maven Central Repository [4],
> > * source code tag "release-2.0.1-rc1" [5],
> > * website pull request listing the new release and adding announcement
> blog
> > post [6].
> >
> > The vote will be open for at least 72 hours. It is adopted by majority
> > approval, with at least 3 PMC affirmative votes.
> >
> >
> > Thanks & Best,
> > Zakelly
> >
> >
> > [1]
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522&version=12355557
> > [2] https://dist.apache.org/repos/dist/dev/flink/flink-2.0.1-rc1/
> > [3] https://dist.apache.org/repos/dist/release/flink/KEYS
> > [4]
> > https://repository.apache.org/content/repositories/orgapacheflink-1866/
> > [5] https://github.com/apache/flink/releases/tag/release-2.0.1-rc1
> > [6] https://github.com/apache/flink-web/pull/813
> >
>

Reply via email to