[RESULT] [VOTE] Release 2.4.0, release candidate #3

I'm happy to announce that we have unanimously approved this release. There are 9 approving votes, 5 of which are binding: * Lukasz Cwik * Ahmet Altay * Robert Bradshaw * Jean-Baptiste Onofré * Ismaël Mejía The strong desire to get the teardown fixes in ASAP was also noted. Thanks everyone!

Re: [VOTE] Release 2.4.0, release candidate #3

+1 (binding) On Tue, Mar 20, 2018 at 10:46 AM Robert Bradshaw wrote: > On Tue, Mar 20, 2018 at 4:08 AM Ismaël Mejía wrote: > >> +1 (binding) >> >> - Validated hashs >> - mvn clean verify -Prelease OK >> - Run nexmark on direct/flink/spark (it works save

Re: [VOTE] Release 2.4.0, release candidate #3

On Tue, Mar 20, 2018 at 4:08 AM Ismaël Mejía wrote: > +1 (binding) > > - Validated hashs > - mvn clean verify -Prelease OK > - Run nexmark on direct/flink/spark (it works save the regression > already tracked on RC2). > > Thanks Robert for being managing the release. > > ps.

Re: [VOTE] Release 2.4.0, release candidate #3

I also tried to run python streaming mobile gaming examples (hourly_team_score, leader_board) on direct runner with little success: https://issues.apache.org/jira/browse/BEAM-3889. I think they escaped our attention on previous release validations. I just tried them with 2.3.0 and didn't have

Re: [VOTE] Release 2.4.0, release candidate #3

+1 (binding) Verified on beam samples (Java) with spark, direct and flink runner. No major change regarding execution time with nexmark. Thanks Regards JB Le 19 mars 2018 à 21:49, à 21:49, Robert Bradshaw a écrit: >Thanks! > >BTW, in case anyone's wondering where the md5

Re: [VOTE] Release 2.4.0, release candidate #3

+1 (binding) I did some more manual validation myself, the burn-down list is empty, and I the artifacts should be correct (though it feels odd to validate that myself, as I'm the one who created them). On Mon, Mar 19, 2018 at 7:22 PM Valentyn Tymofieiev wrote: > +1. > Ran

Re: [VOTE] Release 2.4.0, release candidate #3

+1. Ran a Python Streaming wordcount pipeline on Direct and Dataflow runners and Batch mobile gaming examples on Dataflow runner. On Mon, Mar 19, 2018 at 6:02 PM, Alan Myrvold wrote: > +1 I ran the java quickstarts against 2.4.0 and they passed. > ./gradlew

Re: [VOTE] Release 2.4.0, release candidate #3

I was able to run hourly_team_score. I was passing a wrong argument. No need for an alarm. :) On Mon, Mar 19, 2018 at 5:33 PM, Ahmet Altay wrote: > +1 Thank you Robert. > > Verified python mobile gaming examples using the wheel files on direct > runner. Got user_score working

Re: [VOTE] Release 2.4.0, release candidate #3

+1 Thank you Robert. Verified python mobile gaming examples using the wheel files on direct runner. Got user_score working but hourly_team_score failed with ( https://issues.apache.org/jira/browse/BEAM-3824). Since this is an example, I think it is fine to continue with the release. I will work

Re: [VOTE] Release 2.4.0, release candidate #3

+1, since Tf.Transform 0.6 depends on (and is blocked by) Beam 2.4 On Sat, Mar 17, 2018 at 2:19 AM, Robert Bradshaw wrote: > Hi everyone, > > Please review and vote on the release candidate #3 for the version 2.4.0, > as follows: >

Re: [VOTE] Release 2.4.0, release candidate #3

+1. Verified the Python Quickstart on local and Dataflow (Mac / Linux). Also verified that the Mac / Linux wheels were built correctly with fast / compiled Cython coder support. On Mon, Mar 19, 2018 at 1:49 PM Robert Bradshaw wrote: > Thanks! > > BTW, in case anyone's

Re: [VOTE] Release 2.4.0, release candidate #3

Thanks! BTW, in case anyone's wondering where the md5 files went, they're now discouraged: http://www.apache.org/dev/release-distribution#sigs-and-sums On Mon, Mar 19, 2018 at 12:53 PM Lukasz Cwik wrote: > +1 (binding), verified Java quickstart on Apex local, DirectRunner, >

Re: [VOTE] Release 2.4.0, release candidate #3

+1 (binding), verified Java quickstart on Apex local, DirectRunner, Dataflow, Flink local, Spark local. On Mon, Mar 19, 2018 at 3:54 AM Romain Manni-Bucau wrote: > -0 (cause of the teardown issue which is still a blocker), otherwise > spark/direct runners work in my

Re: [VOTE] Release 2.4.0, release candidate #3

-0 (cause of the teardown issue which is still a blocker), otherwise spark/direct runners work in my projects Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github

[VOTE] Release 2.4.0, release candidate #3

Hi everyone, Please review and vote on the release candidate #3 for the version 2.4.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], *