[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [VOTE] Release 1.5.2, release candidate #2

That is indeed weird. It only seems to affect the source release, will look into it. This also affects 1.6.0 RC1, so it's at least not an issue of my environment.

On 27.07.2018 02:16, Thomas Weise wrote:
+1 but see below

Following shasum verification failed:

FAILED open or read

The problem can be corrected by fixing the file path in
*flink-1.5.2-src.tgz.sha512* - I would recommend doing that before
promoting the release.

Successfully run Beam pipeline against locally running Flink cluster.


On Thu, Jul 26, 2018 at 1:39 AM Chesnay Schepler <chesnay@xxxxxxxxxx> wrote:

Hi everyone,
Please review and vote on the release candidate #2 for the version
1.5.2, 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 11D464BA [3],
* all artifacts to be deployed to the Maven Central Repository [4],
* source code tag "release-1.5.1-rc2" [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.



[2] https://dist.apache.org/repos/dist/dev/flink/flink-1.5.2/
[3] https://dist.apache.org/repos/dist/release/flink/KEYS
[4] https://repository.apache.org/content/repositories/orgapacheflink-1174

[6] https://github.com/apache/flink-web/pull/114