And we found this one[1]. It is an issue that could lead to data 
losing(checkpoint & restoring) when people using the RocksDBBackend, cause by 
the not so nice APIs of RocksIterator...had a hard time to believe it, but this 
seems to affect all the release versions, so I'm not sure whether it's a 
blocker to 1.5.


Best, Sihua
On 05/17/2018 03:27,Till Rohrmann<trohrm...@apache.org> wrote:
Testing the RC has surfaced a problem with the release of blobs of finished
jobs [1]. This is a release blocker and, thus, I have to cancel the RC 3.
I'll prepare a new RC once the problem has been fixed.

Thanks to all for testing the release candidate!

[1] https://issues.apache.org/jira/browse/FLINK-9381?filter=12327438


On Tue, May 15, 2018 at 5:32 PM, Till Rohrmann <trohrm...@apache.org> wrote:

Hi everyone,

Please review and vote on the release candidate #3 for the version 1.5.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 [2], which are signed with the key with
fingerprint 1F302569A96CFFD5 [3],
* all artifacts to be deployed to the Maven Central Repository [4],
* source code tag "release-1.5.0-rc3" [5],

Please use this document for coordinating testing efforts: [6]

The vote will be open for at least 72 hours. It is adopted by majority
approval, with at least 3 PMC affirmative votes.

Your friendly Release Manager

[1] https://issues.apache.org/jira/secure/ReleaseNote.jspa?
[2] http://people.apache.org/~trohrmann/flink-1.5.0-rc3/
[3] https://dist.apache.org/repos/dist/release/flink/KEYS
[4] https://repository.apache.org/content/repositories/orgapacheflink-1156
[5] https://git-wip-us.apache.org/repos/asf?p=flink.git;a=commit;h=
[6] https://docs.google.com/document/d/11DmsJDe-

Pro-tip: you can create a settings.xml file with these contents:


And reference that in you maven commands via --settings
path/to/settings.xml. This is useful for creating a quickstart based on the
staged release and for building against the staged jars.

Reply via email to