+1 (non-binding) I checked: Source release: - SHA512 checksum and GPG signature verified against key EA96AD42DECC72437E0FAC157A366E479A726BA0 (Xiqian YU) from the official KEYS file - LICENSE and NOTICE present; no binaries, no .git directory, no SNAPSHOT dependencies; all POMs consistently point to 3.7.0 - Source tarball matches git tag release-3.7.0-rc1 (commit 045e8da45df4b1017849b04e2d8bfe8f0ed7936d) - Built from source successfully on both baselines: "mvn clean install -DskipTests" (Flink 1.20) and with "-Pflink2" (Flink 2.2) Binary releases: - Both binary tarballs (flink-cdc-3.7.0-1.20 / flink-cdc-3.7.0-2.2): checksums and signatures verified, LICENSE/NOTICE present Maven staging: - orgapacheflink-1944 contains both 3.7.0-1.20 and 3.7.0-2.2 artifacts, complete with signatures and checksums - Successfully resolved a downstream test project against the staged artifacts for both versions (core modules plus mysql/postgres/doris/ starrocks connectors, including all transitive dependencies) Other: - JIRA release notes page accessible and populated - Website PR #884 covers config.toml, release_archive.yml, flink_cdc.yml and the release announcement blog post Minor observation (non-blocking): the dist uber-jar bundles ASM 9.1 (BSD-3-Clause, transitive via Calcite), SLF4J 1.7.36 (MIT) and JTS 1.19.0 (EPL-2.0 / EDL-1.0, newly bundled in 3.7.0 via FLINK-39760), whose license texts are neither shipped in META-INF/licenses/ nor mentioned in the top-level NOTICE (ASM/SLF4J have been like this since 3.6.0). Since JTS is a category-B dependency newly introduced in this release, it would be nice to add the license texts and the corresponding NOTICE entries in a follow-up. Thanks Xiqian for driving this release! Best regards, Yanquan
Xiqian YU <[email protected]> 于2026年9月29日周二 15:15写道： > Hi everyone, > > Please review and vote on the release candidate #1 for the version 3.7.0 > of Apache Flink CDC, > as follows: > > [ ] +1, Approve the release > [ ] -1, Do not approve the release (please provide specific comments) > > **Release Overview** > > As an overview, the release consists of the following: > a) Flink CDC source release to be deployed to dist.apache.org > b) Maven artifacts to be deployed to the Maven Central Repository > > **Staging Areas to Review** > > The staging areas containing the above mentioned artifacts are as follows, > for your review: > * All artifacts for a) can be found in the corresponding dev repository at > dist.apache.org [1], which are signed with the key with fingerprint > EA96AD42DECC72437E0FAC157A366E479A726BA0 [2] > * All artifacts for b) can be found at the Apache Nexus Repository [3] > > Other links for your review: > * JIRA release notes [4] > * Source code tag "release-3.7.0-rc1" with commit hash > 045e8da45df4b1017849b04e2d8bfe8f0ed7936d [5] > * PR for release announcement blog post of Flink CDC 3.7.0 in flink-web [6] > > **Vote Duration** > > The voting time will run for at least 72 hours. > It is adopted by majority approval, with at least 3 PMC affirmative votes. > > Best Regards, > Xiqian > > [1] https://dist.apache.org/repos/dist/dev/flink/flink-cdc-3.7.0-rc1/ > [2] https://dist.apache.org/repos/dist/release/flink/KEYS > [3] > https://repository.apache.org/content/repositories/orgapacheflink-1944/org/apache/flink/ > [4] > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522&version=12356804 > [5] https://github.com/apache/flink-cdc/tree/release-3.7.0-rc1 > [6] https://github.com/apache/flink-web/pull/884
