Hi everyone, Please review and vote on the release candidate 3 for Flink 1.8.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], * the official Apache source release and binary convenience releases to be deployed to dist.apache.org <http://dist.apache.org/> [2], which are signed with the key with fingerprint F2A67A8047499BBB3908D17AA8F4FD97121D7293 [3], * all artifacts to be deployed to the Maven Central Repository [4], * source code tag "release-1.8.0-rc3" [5], * website pull request listing the new release [6] * website pull request adding announcement blog post [7]. The vote will be open for at least 72 hours. It is adopted by majority approval, with at least 3 PMC affirmative votes. Thanks, Aljoscha [1] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522&version=12344274 <https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522&version=12344274> [2] https://dist.apache.org/repos/dist/dev/flink/flink-1.8.0-rc3/ <https://dist.apache.org/repos/dist/dev/flink/flink-1.8.0-rc3/> [3] https://dist.apache.org/repos/dist/release/flink/KEYS <https://dist.apache.org/repos/dist/release/flink/KEYS> [4] https://repository.apache.org/content/repositories/orgapacheflink-1214 <https://repository.apache.org/content/repositories/orgapacheflink-1214> [5] https://gitbox.apache.org/repos/asf?p=flink.git;a=tag;h=b505c0822edd2aed7fa22ed75eca40dca1a9de42 <https://gitbox.apache.org/repos/asf?p=flink.git;a=tag;h=b505c0822edd2aed7fa22ed75eca40dca1a9de42> [6] https://github.com/apache/flink-web/pull/180 <https://github.com/apache/flink-web/pull/180> [7] https://github.com/apache/flink-web/pull/179 <https://github.com/apache/flink-web/pull/179> P.S. The difference to the previous RCs 1 and 2 is very small, you can fetch the tags and do a "git log release-1.8.0-rc1..release-1.8.0-rc3” to see the difference in commits. Its fixes for the issues that led to the cancellation of the previous RCs plus smaller fixes. Most verification/testing that was carried out should apply as is to this RC. Any functional verification that you did on previous RCs should therefore easily carry over to this one.
