Re: [VOTE] Release 1.16.0, release candidate #1

Hi everyone, We have found a blocker issue https://issues.apache.org/jira/browse/FLINK-29567, so the rc1 is officially canceled. And I will prepare the next RC after the blocker issue is resolved. Best, Xingbo Congxian Qiu 于2022年10月10日周一 10:00写道： > +1 (non-binding) > > - checked sha512 & gpg >

Re: [VOTE] Release 1.16.0, release candidate #1

+1 (non-binding) - checked sha512 & gpg - tag in the GitHub repo seems ok - no binary files found in the source - check all versions in the pom file nothing suspicious found - compile from source ok - add one comment about the release blog - deploy standalone session cluster & application job, run

Re: [VOTE] Release 1.16.0, release candidate #1

+1 (non-binding) * Hashes and Signatures look good * All required files on dist.apache.org * Tag is present in Github * Verified source archive does not contain any binary files * Source archive builds using maven * Deployed standalone session cluster and ran TopSpeedWindowing example in streami

Re: [VOTE] Release 1.16.0, release candidate #1

+1 (non-binding) * Downloaded artifacts * Verified checksums/GPG signatures * Compared checkout with provided sources * Verified pom file versions * Went over NOTICE file/pom files changes without finding anything suspicious * Build Flink from sources * Deployed standalone session cluster and ran

Re: [VOTE] Release 1.16.0, release candidate #1

Ok, I was wrong. The step is actually documented at the end of the Flink release documentation [1] in item 15) in the "Checklist to declare the process completed" subsection. I missed that one. Sorry for the confusion. I revoke my veto and close FLINK-29485 [2]. [1] https://cwiki.apache.org/confl

Re: [VOTE] Release 1.16.0, release candidate #1

Probably, my expectations were wrong here: I expected that we want to test the compatibility in these tests between different major versions and that we would want to verify the current version of the release branch as well before releasing the artifacts. What's the rationale behind doing it after

Re: [VOTE] Release 1.16.0, release candidate #1

Could you be more specific as to what you believe should be updated? IIRC the release-1.16 branch only gets updated ta all once the release is out (e.g., mark docs as stable, update japicmp reference). On 30/09/2022 15:32, Matthias Pohl wrote: Looking into the git history, there are numerous

Re: [VOTE] Release 1.16.0, release candidate #1

Looking into the git history, there are numerous locations that need to be updated in the release-1.16 branch. Yun Gao did a few commits around that topic (da9e6be..6f69f4e). But these changes were committed close to the actual release date rather than the release branch creation date. Is this part

Re: [VOTE] Release 1.16.0, release candidate #1

-1 (non-binding) Hi Xingbo, I just noticed that we haven't updated the current Flink version in TypeSerializerUpgradeTest. It is missing in the release-1.16 branch and on master. That means that the serialization tests are not executed for Flink 1.16. See FLINK-29485 [1]. [1] https://issues.apach

[VOTE] Release 1.16.0, release candidate #1

Hi everyone, Please review and vote on the release candidate #1 for the version 1.16.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], *