Re: [RESULT] [VOTE] Release 1.3.3, release candidate #2

2018-03-15 Thread Tzu-Li Tai
The voting time has passed and I'm happy to announce that we've collected enough votes to release this RC as Flink 1.3.3. +1 votes: - Ted (non-binding) - Timo (binding) - Chesnay (binding) - Fabian (binding) - Gordon (binding) - Henry (binding) That's 6 votes, 5 binding. No 0 or -1

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

2018-03-15 Thread Henry Saputra
Signature file looks good Hash files look good LICENSE file exists NOTICE file exists Source artifact build and local tests passed +1 On Wed, Mar 14, 2018 at 3:26 AM, Tzu-Li (Gordon) Tai wrote: > Hi everyone, > > Please review and vote on release candidate #2 for Flink

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

2018-03-15 Thread Tzu-Li (Gordon) Tai
+1 - checked hashes and signatures - built from staged source artifact - ran state machine job chaos monkey test on AWS EMR - ran quickstarts I also agree that we do not need to cancel the RC because of the unintended PythonPlanBinderTest commit. Cheers, Gordon On 15 March 2018 at 11:08:30

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

2018-03-15 Thread Fabian Hueske
+1 - checked hashes and signatures - build from src.tgz with unit tests (mvn clean package) - checked commits for dependency changes and didn't find any Thanks, Fabian 2018-03-15 14:06 GMT+01:00 Chesnay Schepler : > Given that the commit only affects a test I'd be in favor

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

2018-03-15 Thread Chesnay Schepler
Given that the commit only affects a test I'd be in favor of continuing the release process and updating the release notes. On 15.03.2018 14:01, Timo Walther wrote: +1 - built and run tests locally - run some training exercises locally - looked over the commits I found one minor thing that

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

2018-03-15 Thread Timo Walther
+1 - built and run tests locally - run some training exercises locally - looked over the commits I found one minor thing that should be mentioned. It seems that there is one unintended commit in the release: 2455df962c76d20f1c07a57d6ed0118d1d1a067c [FLINK-7283][python] fix

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

2018-03-15 Thread Chesnay Schepler
+1 * verified that compilation works * ran a few test examples against a local cluster * src artifact contains no binaries * verified signatures On 14.03.2018 21:49, Ted Yu wrote: +1 Ran the following command - passed: mvn clean package -Pjdk8 On Wed, Mar 14, 2018 at 3:26 AM, Tzu-Li

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

2018-03-14 Thread Ted Yu
+1 Ran the following command - passed: mvn clean package -Pjdk8 On Wed, Mar 14, 2018 at 3:26 AM, Tzu-Li (Gordon) Tai wrote: > Hi everyone, > > Please review and vote on release candidate #2 for Flink 1.3.3, as > follows: > [ ] +1, Approve the release > [ ] -1, Do not

[VOTE] Release 1.3.3, release candidate #2

2018-03-14 Thread Tzu-Li (Gordon) Tai
Hi everyone, Please review and vote on release candidate #2 for Flink 1.3.3, 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],   *