Hi Ufuk, Thanks for the RC and all the effort that went into the bugfixes :)
I have tested the following things: - Built from source (mvn clean install) - Tested savepoint/restore on both YARN (+HDFS) and standalone - Ran heavy production jobs with pretty much the same build (- the last few commits) for more than a week without any issues The only thing I found is that the fix for [FLINK-5071] has not been backported. (I opened a PR: https://github.com/apache/flink/pull/2990) This can be quite annoying for YARN deployments. I am not sure if this is a blocker though. So +1 from me, except the YARN vcore problem. Cheers, Gyula Ufuk Celebi <u...@apache.org> ezt írta (időpont: 2016. dec. 12., H, 9:28): > Dear Flink community, > > Please vote on releasing the following candidate as Apache Flink version > 1.1.4. > > The commit to be voted on: > a587fe9 (http://git-wip-us.apache.org/repos/asf/flink/commit/a587fe9) > > Branch: > release-1.1.4-rc2 > ( > https://git1-us-west.apache.org/repos/asf/flink/repo?p=flink.git;a=shortlog;h=refs/heads/release-1.1.4-rc2 > ) > > The release artifacts to be voted on can be found at: > http://people.apache.org/~uce/flink-1.1.4-rc2/ > > The release artifacts are signed with the key with fingerprint 9D403309: > http://www.apache.org/dist/flink/KEYS > > The staging repository for this release can be found at: > https://repository.apache.org/content/repositories/orgapacheflink-1108 > > ------------------------------------------------------------- > > The voting time is at least three days and the vote passes if a > majority of at least three +1 PMC votes are cast. The vote ends on > Thursday, December 15th, 2016. > > [ ] +1 Release this package as Apache Flink 1.1.4 > [ ] -1 Do not release this package, because ... > > ------------------------------------------------------------- > > A short notes on testing this RC: A lot of core fixes have been made > for this RC and it is more important than usual to extensively test > this RC. Please have a look at the new commits since 1.1.3 and try to > target the fixes specifically, too. That will be much appreciated and > helpful. >
