+1 - verified checksums and signatures - verified source release matches the tag and contains no binaries - verified LICENSE and NOTICE, RAT check passes - built from source with JDK 11 - verified dist jars match the staging repository - built and installed the Python wheel from the sdist - reviewed the website PR
Best, Weiqing On Tue, Oct 27, 2026 at 6:32 PM Sangkyoon Nam <[email protected]> wrote: > +1 (non-binding) > > - Verified the signatures and SHA512 checksums of the source release, the > Flink 2.3 distribution jar and the Python sdist; the signing key in KEYS > matches 08F0B88DCB04DD4E > - The source release matches tag release-0.4.0-rc1 except for files the > release script excludes (.asf.yaml, .github, .gitignore files, docs/themes) > - LICENSE and NOTICE are present, and the source release contains no .jar, > .class, .so, .whl, .pyc or .zip files > - Built the source release with JDK 21 (mvn clean install -DskipTests) > - Built a wheel from the Python sdist against the staging repository; all > six downloaded jars matched the SHA-256 hashes in jar_manifest.json > - The Flink 2.3 distribution jar on dist matches the staging artifact by > SHA-1, and all 122 staged jar and pom files have .asc, .md5 and .sha1 files > - The Flink 2.3 distribution and thin jars are multi-release jars with the > JDK 21 continuation classes under META-INF/versions/21 > - Checked that the download file names in the website PR match the dist > file names > > I didn't run end-to-end functional tests. > > One upgrade note, not a blocker: in a test-harness check, operator > snapshots taken while an action was still pending didn't restore on the > next release, both from 0.3.0 to 0.4.0-rc1 and from 0.2.1 to 0.3.0. > Snapshots without pending actions restored fine. Since this isn't new in > 0.4, a line clarifying this case in the upgrade notes may be enough for > now, and I'd like to work on making this state restorable for the next > version (https://github.com/apache/flink-agents/discussions/1327). > > Thanks, Wenjin, for driving the release. > > Best, > Sangkyoon > > 2026년 10월 26일 (월) 오후 4:43, wenjin <[email protected]>님이 작성: > > > Hi everyone, > > Please review and vote on the release candidate #1 for the version > > 0.4.0 of Apache Flink Agents, 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: > > * the official Apache Flink Agents source release and binary > > convenience releases > > to be deployed to dist.apache.org [1], which are signed with the key > > with fingerprint 08F0B88DCB04DD4E [2] > > * all artifacts to be deployed to the Maven Central Repository [3], > > * source code tag "release-0.4.0-rc1" [4], > > * website pull request listing the new release and adding announcement > > blog post [5]. > > > > *Please note that Flink Agents 0.4.0 is a preview release and should > > not be used in production environments. Therefore, functionality tests > > should not be the focus of verifications for this release candidate.* > > > > The vote will be open for at least 72 hours. It is adopted by majority > > approval, with at least 3 PMC affirmative votes. > > > > Thanks, > > Wenjin > > > > [1] https://dist.apache.org/repos/dist/dev/flink/flink-agents-0.4.0-rc1/ > > [2] https://dist.apache.org/repos/dist/release/flink/KEYS > > [3] > > https://repository.apache.org/content/repositories/orgapacheflink-1945/ > > [4] https://github.com/apache/flink-agents/tree/release-0.4.0-rc1 > > [5] https://github.com/apache/flink-web/pull/888 > > > > > -- > *남상균 | Sangkyoon Nam* > Staff Engineer, AI-Native Engineering | Building systems that connect > products to people > [email protected] >
