Re: [VOTE] Release 2.3.0, release candidate #1

[Jean-Baptiste Onofré]

Fully agree. Good catch.

I cancel RC1 to prepare a RC2 including at least this fix.

Thanks !
Regards
JB

On 02/01/2018 04:11 PM, Aljoscha Krettek wrote:
> -1
> 
> I think the issue discovered with unbounded sources on Flink Streaming Runner 
> is a serious regression. Good news is that there is already a fix for that: 
> https://github.com/apache/beam/pull/4558/files
> 
> And BEAM-3587 also seems serious enough, IMHO.
> 
> Btw, BEAM-3186, which seems quite serious, was also finally figured out.
> 
> Best,
> Aljoscha
> 
>> On 1. Feb 2018, at 16:00, Jean-Baptiste Onofré  wrote:
>>
>> So, are you casting -1 vote ?
>>
>> I guess so.
>>
>> Regards
>> JB
>>
>> On 02/01/2018 03:53 PM, Ismaël Mejía wrote:
>>> Hi,
>>>
>>> I started to test the release with Nexmark and found three issues
>>> (from minor to more important):
>>>
>>> 1. Small issues to run Nexmark with the release (BEAM-3531 fixed,
>>> BEAM-3592 in PR):
>>>
>>> BEAM-3531 Nexmark failed with NPE with DEFAULT suite
>>> BEAM-3592 Spark-runner profile is broken on Nexmark after move to Spark 2.x
>>>
>>> 2. Flink is broken with Unbounded sources, big enough to deserve a new
>>> vote. Pred:
>>> BEAM-3589 Flink runner breaks with ClassCastException on UnboundedSource
>>>
>>> 3. Direct runner has a relatively big performance regression when
>>> dealing with UnboundedSources. in particular the impact on query 7 of
>>> Nexmark is considerable.
>>>
>>> Just with the small SMOKE suite in my machine I get:
>>>
>>> 
>>> Beam 2.2.0   Beam 2.3.0
>>>  Query  Runtime(sec) Runtime(sec)
>>> 
>>>     6.410.6
>>>  0001   5.110.2
>>>  0002   3.0 5.8
>>>  0003   3.8 6.2
>>>  0004   0.9 1.4
>>>  0005   5.811.4
>>>  0006   0.8 1.4
>>>  0007 193.8  1249.1
>>>  0008   3.9 6.9
>>>  0009   0.9 1.3
>>>  0010   6.4 8.2
>>>  0011   5.0 9.4
>>>  0012   4.7 9.1
>>>
>>> This can be reproduced by running this command:
>>>
>>> mvn exec:java -Dexec.mainClass=org.apache.beam.sdk.nexmark.Main
>>> -Pdirect-runner -Dexec.args="--runner=DirectRunner --suite=SMOKE
>>> --streaming=true --manageResources=false --monitorJobs=true
>>> --enforceEncodability=true --enforceImmutability=true" -pl
>>> 'sdks/java/nexmark'
>>>
>>> I think 2 and 3 deserve to be fixed or at least evaluated as important
>>> enough to cancel the vote. And if possible I would love to cherry-pick
>>> the Nexmark fixes for a future RC.
>>>
>>> On Thu, Feb 1, 2018 at 7:20 AM, Jean-Baptiste Onofré  
>>> wrote:
 Hi all,

 just a quick reminder about the vote process:

 1. Any vote can be changed during the vote period. A -1 vote has to be 
 argued
 (especially if there's not change to do in the project codebase).
 2. For convenience to the release manager, please inform if your vote is 
 binding
 or non-binding (the vote from PMC members are binding)
 3. It's not possible to "veto" a release: if we have at least 3 binding 
 votes,
 the vote can pass.
 4. Please, keep only vote in the thread. If you have some tests in 
 progress,
 please use another thread. It would be great if the thread only contains
 concrete votes.
 5. The vote duration can be extended on request.

 So, I'm extending this vote to 72 more hours to give us time to review
 especially the dataflow worker images test and the Flink TextIO potential 
 issue.

 Thanks !
 Regards
 JB

 On 01/30/2018 09:04 AM, Jean-Baptiste Onofré wrote:
> Hi everyone,
>
> Please review and vote on the release candidate #1 for the version 2.3.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 to be deployed to dist.apache.org 
> [2],
> which is signed with the key with fingerprint C8282E76 [3],
> * all artifacts to be deployed to the Maven Central Repository [4],
> * source code tag "v2.3.0-RC1" [5],
> * website pull request listing the release and publishing the API 
> reference
> manual [6].
> * Java artifacts were built with Maven 3.3.9 and Oracle JDK 1.8.0_111.
> * Python artifacts are deployed along with the source release to the
> dist.apache.org [2].
>
> The vote will be open for at least 72 hours. It is adopted by majority 
> approval,
> with at least 3 PMC affirmative votes.
>
> Thanks,
> JB
>
> [1]
> 

Re: [VOTE] Release 2.3.0, release candidate #1

[Aljoscha Krettek]

-1

I think the issue discovered with unbounded sources on Flink Streaming Runner 
is a serious regression. Good news is that there is already a fix for that: 
https://github.com/apache/beam/pull/4558/files

And BEAM-3587 also seems serious enough, IMHO.

Btw, BEAM-3186, which seems quite serious, was also finally figured out.

Best,
Aljoscha

> On 1. Feb 2018, at 16:00, Jean-Baptiste Onofré  wrote:
> 
> So, are you casting -1 vote ?
> 
> I guess so.
> 
> Regards
> JB
> 
> On 02/01/2018 03:53 PM, Ismaël Mejía wrote:
>> Hi,
>> 
>> I started to test the release with Nexmark and found three issues
>> (from minor to more important):
>> 
>> 1. Small issues to run Nexmark with the release (BEAM-3531 fixed,
>> BEAM-3592 in PR):
>> 
>> BEAM-3531 Nexmark failed with NPE with DEFAULT suite
>> BEAM-3592 Spark-runner profile is broken on Nexmark after move to Spark 2.x
>> 
>> 2. Flink is broken with Unbounded sources, big enough to deserve a new
>> vote. Pred:
>> BEAM-3589 Flink runner breaks with ClassCastException on UnboundedSource
>> 
>> 3. Direct runner has a relatively big performance regression when
>> dealing with UnboundedSources. in particular the impact on query 7 of
>> Nexmark is considerable.
>> 
>> Just with the small SMOKE suite in my machine I get:
>> 
>> 
>> Beam 2.2.0   Beam 2.3.0
>>  Query  Runtime(sec) Runtime(sec)
>> 
>>     6.410.6
>>  0001   5.110.2
>>  0002   3.0 5.8
>>  0003   3.8 6.2
>>  0004   0.9 1.4
>>  0005   5.811.4
>>  0006   0.8 1.4
>>  0007 193.8  1249.1
>>  0008   3.9 6.9
>>  0009   0.9 1.3
>>  0010   6.4 8.2
>>  0011   5.0 9.4
>>  0012   4.7 9.1
>> 
>> This can be reproduced by running this command:
>> 
>> mvn exec:java -Dexec.mainClass=org.apache.beam.sdk.nexmark.Main
>> -Pdirect-runner -Dexec.args="--runner=DirectRunner --suite=SMOKE
>> --streaming=true --manageResources=false --monitorJobs=true
>> --enforceEncodability=true --enforceImmutability=true" -pl
>> 'sdks/java/nexmark'
>> 
>> I think 2 and 3 deserve to be fixed or at least evaluated as important
>> enough to cancel the vote. And if possible I would love to cherry-pick
>> the Nexmark fixes for a future RC.
>> 
>> On Thu, Feb 1, 2018 at 7:20 AM, Jean-Baptiste Onofré  
>> wrote:
>>> Hi all,
>>> 
>>> just a quick reminder about the vote process:
>>> 
>>> 1. Any vote can be changed during the vote period. A -1 vote has to be 
>>> argued
>>> (especially if there's not change to do in the project codebase).
>>> 2. For convenience to the release manager, please inform if your vote is 
>>> binding
>>> or non-binding (the vote from PMC members are binding)
>>> 3. It's not possible to "veto" a release: if we have at least 3 binding 
>>> votes,
>>> the vote can pass.
>>> 4. Please, keep only vote in the thread. If you have some tests in progress,
>>> please use another thread. It would be great if the thread only contains
>>> concrete votes.
>>> 5. The vote duration can be extended on request.
>>> 
>>> So, I'm extending this vote to 72 more hours to give us time to review
>>> especially the dataflow worker images test and the Flink TextIO potential 
>>> issue.
>>> 
>>> Thanks !
>>> Regards
>>> JB
>>> 
>>> On 01/30/2018 09:04 AM, Jean-Baptiste Onofré wrote:
 Hi everyone,
 
 Please review and vote on the release candidate #1 for the version 2.3.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 to be deployed to dist.apache.org [2],
 which is signed with the key with fingerprint C8282E76 [3],
 * all artifacts to be deployed to the Maven Central Repository [4],
 * source code tag "v2.3.0-RC1" [5],
 * website pull request listing the release and publishing the API reference
 manual [6].
 * Java artifacts were built with Maven 3.3.9 and Oracle JDK 1.8.0_111.
 * Python artifacts are deployed along with the source release to the
 dist.apache.org [2].
 
 The vote will be open for at least 72 hours. It is adopted by majority 
 approval,
 with at least 3 PMC affirmative votes.
 
 Thanks,
 JB
 
 [1]
 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527=12341608
 [2] https://dist.apache.org/repos/dist/dev/beam/2.3.0/
 [3] https://dist.apache.org/repos/dist/release/beam/KEYS
 [4] https://repository.apache.org/content/repositories/orgapachebeam-1026/
 [5] 

Re: [VOTE] Release 2.3.0, release candidate #1

[Jean-Baptiste Onofré]

So, are you casting -1 vote ?

I guess so.

Regards
JB

On 02/01/2018 03:53 PM, Ismaël Mejía wrote:
> Hi,
> 
> I started to test the release with Nexmark and found three issues
> (from minor to more important):
> 
> 1. Small issues to run Nexmark with the release (BEAM-3531 fixed,
> BEAM-3592 in PR):
> 
> BEAM-3531 Nexmark failed with NPE with DEFAULT suite
> BEAM-3592 Spark-runner profile is broken on Nexmark after move to Spark 2.x
> 
> 2. Flink is broken with Unbounded sources, big enough to deserve a new
> vote. Pred:
> BEAM-3589 Flink runner breaks with ClassCastException on UnboundedSource
> 
> 3. Direct runner has a relatively big performance regression when
> dealing with UnboundedSources. in particular the impact on query 7 of
> Nexmark is considerable.
> 
> Just with the small SMOKE suite in my machine I get:
> 
> 
>  Beam 2.2.0   Beam 2.3.0
>   Query  Runtime(sec) Runtime(sec)
> 
>      6.410.6
>   0001   5.110.2
>   0002   3.0 5.8
>   0003   3.8 6.2
>   0004   0.9 1.4
>   0005   5.811.4
>   0006   0.8 1.4
>   0007 193.8  1249.1
>   0008   3.9 6.9
>   0009   0.9 1.3
>   0010   6.4 8.2
>   0011   5.0 9.4
>   0012   4.7 9.1
> 
> This can be reproduced by running this command:
> 
> mvn exec:java -Dexec.mainClass=org.apache.beam.sdk.nexmark.Main
> -Pdirect-runner -Dexec.args="--runner=DirectRunner --suite=SMOKE
> --streaming=true --manageResources=false --monitorJobs=true
> --enforceEncodability=true --enforceImmutability=true" -pl
> 'sdks/java/nexmark'
> 
> I think 2 and 3 deserve to be fixed or at least evaluated as important
> enough to cancel the vote. And if possible I would love to cherry-pick
> the Nexmark fixes for a future RC.
> 
> On Thu, Feb 1, 2018 at 7:20 AM, Jean-Baptiste Onofré  
> wrote:
>> Hi all,
>>
>> just a quick reminder about the vote process:
>>
>> 1. Any vote can be changed during the vote period. A -1 vote has to be argued
>> (especially if there's not change to do in the project codebase).
>> 2. For convenience to the release manager, please inform if your vote is 
>> binding
>> or non-binding (the vote from PMC members are binding)
>> 3. It's not possible to "veto" a release: if we have at least 3 binding 
>> votes,
>> the vote can pass.
>> 4. Please, keep only vote in the thread. If you have some tests in progress,
>> please use another thread. It would be great if the thread only contains
>> concrete votes.
>> 5. The vote duration can be extended on request.
>>
>> So, I'm extending this vote to 72 more hours to give us time to review
>> especially the dataflow worker images test and the Flink TextIO potential 
>> issue.
>>
>> Thanks !
>> Regards
>> JB
>>
>> On 01/30/2018 09:04 AM, Jean-Baptiste Onofré wrote:
>>> Hi everyone,
>>>
>>> Please review and vote on the release candidate #1 for the version 2.3.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 to be deployed to dist.apache.org [2],
>>> which is signed with the key with fingerprint C8282E76 [3],
>>> * all artifacts to be deployed to the Maven Central Repository [4],
>>> * source code tag "v2.3.0-RC1" [5],
>>> * website pull request listing the release and publishing the API reference
>>> manual [6].
>>> * Java artifacts were built with Maven 3.3.9 and Oracle JDK 1.8.0_111.
>>> * Python artifacts are deployed along with the source release to the
>>> dist.apache.org [2].
>>>
>>> The vote will be open for at least 72 hours. It is adopted by majority 
>>> approval,
>>> with at least 3 PMC affirmative votes.
>>>
>>> Thanks,
>>> JB
>>>
>>> [1]
>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527=12341608
>>> [2] https://dist.apache.org/repos/dist/dev/beam/2.3.0/
>>> [3] https://dist.apache.org/repos/dist/release/beam/KEYS
>>> [4] https://repository.apache.org/content/repositories/orgapachebeam-1026/
>>> [5] https://github.com/apache/beam/tree/v2.3.0-RC1
>>> [6] https://github.com/apache/beam-site/pull/381
>>>
>>
>> --
>> Jean-Baptiste Onofré
>> jbono...@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [VOTE] Release 2.3.0, release candidate #1

[Ismaël Mejía]

Hi,

I started to test the release with Nexmark and found three issues
(from minor to more important):

1. Small issues to run Nexmark with the release (BEAM-3531 fixed,
BEAM-3592 in PR):

BEAM-3531 Nexmark failed with NPE with DEFAULT suite
BEAM-3592 Spark-runner profile is broken on Nexmark after move to Spark 2.x

2. Flink is broken with Unbounded sources, big enough to deserve a new
vote. Pred:
BEAM-3589 Flink runner breaks with ClassCastException on UnboundedSource

3. Direct runner has a relatively big performance regression when
dealing with UnboundedSources. in particular the impact on query 7 of
Nexmark is considerable.

Just with the small SMOKE suite in my machine I get:


 Beam 2.2.0   Beam 2.3.0
  Query  Runtime(sec) Runtime(sec)

     6.410.6
  0001   5.110.2
  0002   3.0 5.8
  0003   3.8 6.2
  0004   0.9 1.4
  0005   5.811.4
  0006   0.8 1.4
  0007 193.8  1249.1
  0008   3.9 6.9
  0009   0.9 1.3
  0010   6.4 8.2
  0011   5.0 9.4
  0012   4.7 9.1

This can be reproduced by running this command:

mvn exec:java -Dexec.mainClass=org.apache.beam.sdk.nexmark.Main
-Pdirect-runner -Dexec.args="--runner=DirectRunner --suite=SMOKE
--streaming=true --manageResources=false --monitorJobs=true
--enforceEncodability=true --enforceImmutability=true" -pl
'sdks/java/nexmark'

I think 2 and 3 deserve to be fixed or at least evaluated as important
enough to cancel the vote. And if possible I would love to cherry-pick
the Nexmark fixes for a future RC.

On Thu, Feb 1, 2018 at 7:20 AM, Jean-Baptiste Onofré  wrote:
> Hi all,
>
> just a quick reminder about the vote process:
>
> 1. Any vote can be changed during the vote period. A -1 vote has to be argued
> (especially if there's not change to do in the project codebase).
> 2. For convenience to the release manager, please inform if your vote is 
> binding
> or non-binding (the vote from PMC members are binding)
> 3. It's not possible to "veto" a release: if we have at least 3 binding votes,
> the vote can pass.
> 4. Please, keep only vote in the thread. If you have some tests in progress,
> please use another thread. It would be great if the thread only contains
> concrete votes.
> 5. The vote duration can be extended on request.
>
> So, I'm extending this vote to 72 more hours to give us time to review
> especially the dataflow worker images test and the Flink TextIO potential 
> issue.
>
> Thanks !
> Regards
> JB
>
> On 01/30/2018 09:04 AM, Jean-Baptiste Onofré wrote:
>> Hi everyone,
>>
>> Please review and vote on the release candidate #1 for the version 2.3.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 to be deployed to dist.apache.org [2],
>> which is signed with the key with fingerprint C8282E76 [3],
>> * all artifacts to be deployed to the Maven Central Repository [4],
>> * source code tag "v2.3.0-RC1" [5],
>> * website pull request listing the release and publishing the API reference
>> manual [6].
>> * Java artifacts were built with Maven 3.3.9 and Oracle JDK 1.8.0_111.
>> * Python artifacts are deployed along with the source release to the
>> dist.apache.org [2].
>>
>> The vote will be open for at least 72 hours. It is adopted by majority 
>> approval,
>> with at least 3 PMC affirmative votes.
>>
>> Thanks,
>> JB
>>
>> [1]
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527=12341608
>> [2] https://dist.apache.org/repos/dist/dev/beam/2.3.0/
>> [3] https://dist.apache.org/repos/dist/release/beam/KEYS
>> [4] https://repository.apache.org/content/repositories/orgapachebeam-1026/
>> [5] https://github.com/apache/beam/tree/v2.3.0-RC1
>> [6] https://github.com/apache/beam-site/pull/381
>>
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com

Re: [VOTE] Release 2.3.0, release candidate #1

[Jean-Baptiste Onofré]

Hi all,

just a quick reminder about the vote process:

1. Any vote can be changed during the vote period. A -1 vote has to be argued
(especially if there's not change to do in the project codebase).
2. For convenience to the release manager, please inform if your vote is binding
or non-binding (the vote from PMC members are binding)
3. It's not possible to "veto" a release: if we have at least 3 binding votes,
the vote can pass.
4. Please, keep only vote in the thread. If you have some tests in progress,
please use another thread. It would be great if the thread only contains
concrete votes.
5. The vote duration can be extended on request.

So, I'm extending this vote to 72 more hours to give us time to review
especially the dataflow worker images test and the Flink TextIO potential issue.

Thanks !
Regards
JB

On 01/30/2018 09:04 AM, Jean-Baptiste Onofré wrote:
> Hi everyone,
> 
> Please review and vote on the release candidate #1 for the version 2.3.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 to be deployed to dist.apache.org [2],
> which is signed with the key with fingerprint C8282E76 [3],
> * all artifacts to be deployed to the Maven Central Repository [4],
> * source code tag "v2.3.0-RC1" [5],
> * website pull request listing the release and publishing the API reference
> manual [6].
> * Java artifacts were built with Maven 3.3.9 and Oracle JDK 1.8.0_111.
> * Python artifacts are deployed along with the source release to the
> dist.apache.org [2].
> 
> The vote will be open for at least 72 hours. It is adopted by majority 
> approval,
> with at least 3 PMC affirmative votes.
> 
> Thanks,
> JB
> 
> [1]
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527=12341608
> [2] https://dist.apache.org/repos/dist/dev/beam/2.3.0/
> [3] https://dist.apache.org/repos/dist/release/beam/KEYS
> [4] https://repository.apache.org/content/repositories/orgapachebeam-1026/
> [5] https://github.com/apache/beam/tree/v2.3.0-RC1
> [6] https://github.com/apache/beam-site/pull/381
> 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [VOTE] Release 2.3.0, release candidate #1

[Romain Manni-Bucau]

@ismael: any vote can be changes from -1 to +1 (or +-0) without additional
delay

Le 1 févr. 2018 03:15, "Lukasz Cwik"  a écrit :

> Note that a user reported TextIO being broken on Flink.
> Thread is here: https://lists.apache.org/thread.html/
> 47b16c94032392782505415e010970fd2a9480891c55c2f7b5de92bd@%
> 3Cuser.beam.apache.org%3E
> Can someone confirm/refute?
>
> On Wed, Jan 31, 2018 at 3:36 PM, Konstantinos Katsiapis <
> katsia...@google.com> wrote:
>
>> +1 (non-binding). tensorflow.transform
>>  0.5.0 is blocked on Apache
>> Beam 2.3
>>
>>
>> On Wed, Jan 31, 2018 at 5:59 AM, Jean-Baptiste Onofré 
>> wrote:
>>
>>> +1 (binding)
>>>
>>> Casting my own +1 ;)
>>>
>>> Regards
>>> JB
>>>
>>> On 01/30/2018 09:04 AM, Jean-Baptiste Onofré wrote:
>>> > Hi everyone,
>>> >
>>> > Please review and vote on the release candidate #1 for the version
>>> 2.3.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 to be deployed to dist.apache.org
>>> [2],
>>> > which is signed with the key with fingerprint C8282E76 [3],
>>> > * all artifacts to be deployed to the Maven Central Repository [4],
>>> > * source code tag "v2.3.0-RC1" [5],
>>> > * website pull request listing the release and publishing the API
>>> reference
>>> > manual [6].
>>> > * Java artifacts were built with Maven 3.3.9 and Oracle JDK 1.8.0_111.
>>> > * Python artifacts are deployed along with the source release to the
>>> > dist.apache.org [2].
>>> >
>>> > The vote will be open for at least 72 hours. It is adopted by majority
>>> approval,
>>> > with at least 3 PMC affirmative votes.
>>> >
>>> > Thanks,
>>> > JB
>>> >
>>> > [1]
>>> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
>>> ctId=12319527=12341608
>>> > [2] https://dist.apache.org/repos/dist/dev/beam/2.3.0/
>>> > [3] https://dist.apache.org/repos/dist/release/beam/KEYS
>>> > [4] https://repository.apache.org/content/repositories/orgapache
>>> beam-1026/
>>> > [5] https://github.com/apache/beam/tree/v2.3.0-RC1
>>> > [6] https://github.com/apache/beam-site/pull/381
>>> >
>>>
>>> --
>>> Jean-Baptiste Onofré
>>> jbono...@apache.org
>>> http://blog.nanthrax.net
>>> Talend - http://www.talend.com
>>>
>>
>>
>>
>> --
>> Gus Katsiapis | Software Engineer | katsia...@google.com | 650-918-7487
>> <(650)%20918-7487>
>>
>
>

Re: [VOTE] Release 2.3.0, release candidate #1

[Lukasz Cwik]

Note that a user reported TextIO being broken on Flink.
Thread is here:
https://lists.apache.org/thread.html/47b16c94032392782505415e010970fd2a9480891c55c2f7b5de92bd@%3Cuser.beam.apache.org%3E
Can someone confirm/refute?

On Wed, Jan 31, 2018 at 3:36 PM, Konstantinos Katsiapis <
katsia...@google.com> wrote:

> +1 (non-binding). tensorflow.transform
>  0.5.0 is blocked on Apache Beam
> 2.3
>
>
> On Wed, Jan 31, 2018 at 5:59 AM, Jean-Baptiste Onofré 
> wrote:
>
>> +1 (binding)
>>
>> Casting my own +1 ;)
>>
>> Regards
>> JB
>>
>> On 01/30/2018 09:04 AM, Jean-Baptiste Onofré wrote:
>> > Hi everyone,
>> >
>> > Please review and vote on the release candidate #1 for the version
>> 2.3.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 to be deployed to dist.apache.org
>> [2],
>> > which is signed with the key with fingerprint C8282E76 [3],
>> > * all artifacts to be deployed to the Maven Central Repository [4],
>> > * source code tag "v2.3.0-RC1" [5],
>> > * website pull request listing the release and publishing the API
>> reference
>> > manual [6].
>> > * Java artifacts were built with Maven 3.3.9 and Oracle JDK 1.8.0_111.
>> > * Python artifacts are deployed along with the source release to the
>> > dist.apache.org [2].
>> >
>> > The vote will be open for at least 72 hours. It is adopted by majority
>> approval,
>> > with at least 3 PMC affirmative votes.
>> >
>> > Thanks,
>> > JB
>> >
>> > [1]
>> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
>> ctId=12319527=12341608
>> > [2] https://dist.apache.org/repos/dist/dev/beam/2.3.0/
>> > [3] https://dist.apache.org/repos/dist/release/beam/KEYS
>> > [4] https://repository.apache.org/content/repositories/orgapache
>> beam-1026/
>> > [5] https://github.com/apache/beam/tree/v2.3.0-RC1
>> > [6] https://github.com/apache/beam-site/pull/381
>> >
>>
>> --
>> Jean-Baptiste Onofré
>> jbono...@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>
>
>
> --
> Gus Katsiapis | Software Engineer | katsia...@google.com | 650-918-7487
> <(650)%20918-7487>
>

Re: [VOTE] Release 2.3.0, release candidate #1

[Ahmet Altay]

This will require a change in the Beam code, because image names are
hardcoded in to code (python) and configuration (java). RC1 as it is will
not work correctly with Cloud Dataflow.

On Wed, Jan 31, 2018 at 2:08 PM, Reuven Lax  wrote:

> Hopefully we can validate soon. I believe some of the delays are because
> of integrating major changes done over the last week (e.g. Java 8
> migration).
>
> On Wed, Jan 31, 2018 at 2:04 PM, Ismaël Mejía  wrote:
>
>> What is the common procedure in cases like this ? Because it doesn't
>> seems that it needs a re-vote, just an extra day or two for
>> validation, any ideas JB ?
>>
>> On Wed, Jan 31, 2018 at 10:41 PM, Alan Myrvold 
>> wrote:
>> > Yes, it is a dataflow step. Happy to test this again when they are
>> > available.
>> >
>> > On Wed, Jan 31, 2018 at 1:39 PM, Jean-Baptiste Onofré 
>> > wrote:
>> >>
>> >> OK, I think I understood ;)
>> >>
>> >> So it's not "directly" related to Beam itself (it's more a Dataflow
>> step
>> >> to perform).
>> >>
>> >> @Alan, I think it's better to test first and then cast the vote. This
>> kind
>> >> of tests are valuable to validate the release and make sense. But vote
>> >> should represent the state of the Beam release. So I think -1 vote is
>> a bit
>> >> too early before the test.
>> >>
>> >> Thanks !
>> >> Regards
>> >> JB
>> >>
>> >> On 31/01/2018 22:33, Reuven Lax wrote:
>> >>>
>> >>> It's just a step that needs to be peformed before the new release
>> works
>> >>> on Dataflow. Alan is saying that we've been unable to validate
>> Dataflow so
>> >>> far, as worker images are not yet built. Hopefully they'll be built
>> soon,
>> >>> and we'll be able to validate.
>> >>>
>> >>> On Wed, Jan 31, 2018 at 1:31 PM, Jean-Baptiste Onofré <
>> j...@nanthrax.net
>> >>> > wrote:
>> >>>
>> >>> Hi Alan
>> >>>
>> >>> does it related to change in the codebase or in a
>> dependency/related
>> >>> project ?
>> >>>
>> >>> I mean: is it something we have to fix/change in Beam ?
>> >>>
>> >>> Just curious as I'm not sure what you mean by "worker images" ;)
>> >>>
>> >>> Thanks !
>> >>> Regards
>> >>> JB
>> >>>
>> >>> On 31/01/2018 22:18, Alan Myrvold wrote:
>> >>>
>> >>> -1 (for now, hope to change this)
>> >>>
>> >>> Dataflow runner jobs are failing for me with 2.3.0 RC1, for
>> both
>> >>> Java and Python.
>> >>>
>> >>> This is not an issues with the 2.3.0 RC1 SDK, we (google) need
>> >>> to release worker images.
>> >>>
>> >>> I have assigned these bugs to myself, and will be working to
>> >>> help get these workers released.
>> >>>
>> >>> [BEAM-3584] Java dataflow job fails with 2.3.0 RC1, due to
>> >>> missing worker image
>> >>> [BEAM-3585] Python dataflow job fails with 2.3.0 RC1, due to
>> >>> missing worker image
>> >>>
>> >>> On Wed, Jan 31, 2018 at 6:12 AM, Jean-Baptiste Onofré
>> >>> 
>> >>> >> wrote:
>> >>>
>> >>>  Thanks Kenn,
>> >>>
>> >>>  I prepared the list of tasks I did. I will complete where
>> >>> release is
>> >>>  out.
>> >>>
>> >>>  Regards
>> >>>  JB
>> >>>
>> >>>  On 01/31/2018 03:07 PM, Kenneth Knowles wrote:
>> >>>  > I've cloned the release validation spreadsheet:
>> >>>  >
>> >>>  > https://s.apache.org/beam-2.3.0-release-validation
>> >>> 
>> >>>  > >>> >
>> >>>  >
>> >>>  > If you plan to perform a manual validation task, please
>> >>> sign up so multiple
>> >>>  > people don't waste effort.
>> >>>  >
>> >>>  > Alan & JB, as far as your pairing up to automate more,
>> >>> anything manual on this
>> >>>  > sheet should be considered.
>> >>>  >
>> >>>  > Kenn
>> >>>  >
>> >>>  > On Wed, Jan 31, 2018 at 5:59 AM, Jean-Baptiste Onofré
>> >>> 
>> >>> >
>> >>>  > 
>> >>> > >>>  >
>> >>>  > +1 (binding)
>> >>>  >
>> >>>  > Casting my own +1 ;)
>> >>>  >
>> >>>  > Regards
>> >>>  > JB
>> >>>  >
>> >>>  > On 01/30/2018 09:04 AM, Jean-Baptiste Onofré wrote:
>> >>>  > > 

Re: [VOTE] Release 2.3.0, release candidate #1

[Reuven Lax]

Hopefully we can validate soon. I believe some of the delays are because of
integrating major changes done over the last week (e.g. Java 8 migration).

On Wed, Jan 31, 2018 at 2:04 PM, Ismaël Mejía  wrote:

> What is the common procedure in cases like this ? Because it doesn't
> seems that it needs a re-vote, just an extra day or two for
> validation, any ideas JB ?
>
> On Wed, Jan 31, 2018 at 10:41 PM, Alan Myrvold 
> wrote:
> > Yes, it is a dataflow step. Happy to test this again when they are
> > available.
> >
> > On Wed, Jan 31, 2018 at 1:39 PM, Jean-Baptiste Onofré 
> > wrote:
> >>
> >> OK, I think I understood ;)
> >>
> >> So it's not "directly" related to Beam itself (it's more a Dataflow step
> >> to perform).
> >>
> >> @Alan, I think it's better to test first and then cast the vote. This
> kind
> >> of tests are valuable to validate the release and make sense. But vote
> >> should represent the state of the Beam release. So I think -1 vote is a
> bit
> >> too early before the test.
> >>
> >> Thanks !
> >> Regards
> >> JB
> >>
> >> On 31/01/2018 22:33, Reuven Lax wrote:
> >>>
> >>> It's just a step that needs to be peformed before the new release works
> >>> on Dataflow. Alan is saying that we've been unable to validate
> Dataflow so
> >>> far, as worker images are not yet built. Hopefully they'll be built
> soon,
> >>> and we'll be able to validate.
> >>>
> >>> On Wed, Jan 31, 2018 at 1:31 PM, Jean-Baptiste Onofré  >>> > wrote:
> >>>
> >>> Hi Alan
> >>>
> >>> does it related to change in the codebase or in a
> dependency/related
> >>> project ?
> >>>
> >>> I mean: is it something we have to fix/change in Beam ?
> >>>
> >>> Just curious as I'm not sure what you mean by "worker images" ;)
> >>>
> >>> Thanks !
> >>> Regards
> >>> JB
> >>>
> >>> On 31/01/2018 22:18, Alan Myrvold wrote:
> >>>
> >>> -1 (for now, hope to change this)
> >>>
> >>> Dataflow runner jobs are failing for me with 2.3.0 RC1, for
> both
> >>> Java and Python.
> >>>
> >>> This is not an issues with the 2.3.0 RC1 SDK, we (google) need
> >>> to release worker images.
> >>>
> >>> I have assigned these bugs to myself, and will be working to
> >>> help get these workers released.
> >>>
> >>> [BEAM-3584] Java dataflow job fails with 2.3.0 RC1, due to
> >>> missing worker image
> >>> [BEAM-3585] Python dataflow job fails with 2.3.0 RC1, due to
> >>> missing worker image
> >>>
> >>> On Wed, Jan 31, 2018 at 6:12 AM, Jean-Baptiste Onofré
> >>> 
> >>> >> wrote:
> >>>
> >>>  Thanks Kenn,
> >>>
> >>>  I prepared the list of tasks I did. I will complete where
> >>> release is
> >>>  out.
> >>>
> >>>  Regards
> >>>  JB
> >>>
> >>>  On 01/31/2018 03:07 PM, Kenneth Knowles wrote:
> >>>  > I've cloned the release validation spreadsheet:
> >>>  >
> >>>  > https://s.apache.org/beam-2.3.0-release-validation
> >>> 
> >>>   >>> >
> >>>  >
> >>>  > If you plan to perform a manual validation task, please
> >>> sign up so multiple
> >>>  > people don't waste effort.
> >>>  >
> >>>  > Alan & JB, as far as your pairing up to automate more,
> >>> anything manual on this
> >>>  > sheet should be considered.
> >>>  >
> >>>  > Kenn
> >>>  >
> >>>  > On Wed, Jan 31, 2018 at 5:59 AM, Jean-Baptiste Onofré
> >>> 
> >>> >
> >>>  > 
> >>>  >>>  >
> >>>  > +1 (binding)
> >>>  >
> >>>  > Casting my own +1 ;)
> >>>  >
> >>>  > Regards
> >>>  > JB
> >>>  >
> >>>  > On 01/30/2018 09:04 AM, Jean-Baptiste Onofré wrote:
> >>>  > > Hi everyone,
> >>>  > >
> >>>  > > Please review and vote on the release candidate #1
> >>> for the version 2.3.0, as
> >>>  > > follows:
> >>>  > >
> >>>  > > [ ] +1, Approve the release
> >>>  > > [ ] -1, Do not approve the release (please provide
> >>> specific comments)
> >>>  

Re: [VOTE] Release 2.3.0, release candidate #1

[Ismaël Mejía]

What is the common procedure in cases like this ? Because it doesn't
seems that it needs a re-vote, just an extra day or two for
validation, any ideas JB ?

On Wed, Jan 31, 2018 at 10:41 PM, Alan Myrvold  wrote:
> Yes, it is a dataflow step. Happy to test this again when they are
> available.
>
> On Wed, Jan 31, 2018 at 1:39 PM, Jean-Baptiste Onofré 
> wrote:
>>
>> OK, I think I understood ;)
>>
>> So it's not "directly" related to Beam itself (it's more a Dataflow step
>> to perform).
>>
>> @Alan, I think it's better to test first and then cast the vote. This kind
>> of tests are valuable to validate the release and make sense. But vote
>> should represent the state of the Beam release. So I think -1 vote is a bit
>> too early before the test.
>>
>> Thanks !
>> Regards
>> JB
>>
>> On 31/01/2018 22:33, Reuven Lax wrote:
>>>
>>> It's just a step that needs to be peformed before the new release works
>>> on Dataflow. Alan is saying that we've been unable to validate Dataflow so
>>> far, as worker images are not yet built. Hopefully they'll be built soon,
>>> and we'll be able to validate.
>>>
>>> On Wed, Jan 31, 2018 at 1:31 PM, Jean-Baptiste Onofré >> > wrote:
>>>
>>> Hi Alan
>>>
>>> does it related to change in the codebase or in a dependency/related
>>> project ?
>>>
>>> I mean: is it something we have to fix/change in Beam ?
>>>
>>> Just curious as I'm not sure what you mean by "worker images" ;)
>>>
>>> Thanks !
>>> Regards
>>> JB
>>>
>>> On 31/01/2018 22:18, Alan Myrvold wrote:
>>>
>>> -1 (for now, hope to change this)
>>>
>>> Dataflow runner jobs are failing for me with 2.3.0 RC1, for both
>>> Java and Python.
>>>
>>> This is not an issues with the 2.3.0 RC1 SDK, we (google) need
>>> to release worker images.
>>>
>>> I have assigned these bugs to myself, and will be working to
>>> help get these workers released.
>>>
>>> [BEAM-3584] Java dataflow job fails with 2.3.0 RC1, due to
>>> missing worker image
>>> [BEAM-3585] Python dataflow job fails with 2.3.0 RC1, due to
>>> missing worker image
>>>
>>> On Wed, Jan 31, 2018 at 6:12 AM, Jean-Baptiste Onofré
>>> 
>>> >> wrote:
>>>
>>>  Thanks Kenn,
>>>
>>>  I prepared the list of tasks I did. I will complete where
>>> release is
>>>  out.
>>>
>>>  Regards
>>>  JB
>>>
>>>  On 01/31/2018 03:07 PM, Kenneth Knowles wrote:
>>>  > I've cloned the release validation spreadsheet:
>>>  >
>>>  > https://s.apache.org/beam-2.3.0-release-validation
>>> 
>>>  >> >
>>>  >
>>>  > If you plan to perform a manual validation task, please
>>> sign up so multiple
>>>  > people don't waste effort.
>>>  >
>>>  > Alan & JB, as far as your pairing up to automate more,
>>> anything manual on this
>>>  > sheet should be considered.
>>>  >
>>>  > Kenn
>>>  >
>>>  > On Wed, Jan 31, 2018 at 5:59 AM, Jean-Baptiste Onofré
>>> 
>>> >
>>>  > 
>>> >>  >
>>>  > +1 (binding)
>>>  >
>>>  > Casting my own +1 ;)
>>>  >
>>>  > Regards
>>>  > JB
>>>  >
>>>  > On 01/30/2018 09:04 AM, Jean-Baptiste Onofré wrote:
>>>  > > Hi everyone,
>>>  > >
>>>  > > Please review and vote on the release candidate #1
>>> for the version 2.3.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 to be deployed
>>> to dist.apache.org 
>>> 
>>>   >  [2],
>>>  > > which is signed with the key with 

Re: [VOTE] Release 2.3.0, release candidate #1

[Alan Myrvold]

Yes, it is a dataflow step. Happy to test this again when they are
available.

On Wed, Jan 31, 2018 at 1:39 PM, Jean-Baptiste Onofré 
wrote:

> OK, I think I understood ;)
>
> So it's not "directly" related to Beam itself (it's more a Dataflow step
> to perform).
>
> @Alan, I think it's better to test first and then cast the vote. This kind
> of tests are valuable to validate the release and make sense. But vote
> should represent the state of the Beam release. So I think -1 vote is a bit
> too early before the test.
>
> Thanks !
> Regards
> JB
>
> On 31/01/2018 22:33, Reuven Lax wrote:
>
>> It's just a step that needs to be peformed before the new release works
>> on Dataflow. Alan is saying that we've been unable to validate Dataflow so
>> far, as worker images are not yet built. Hopefully they'll be built soon,
>> and we'll be able to validate.
>>
>> On Wed, Jan 31, 2018 at 1:31 PM, Jean-Baptiste Onofré > > wrote:
>>
>> Hi Alan
>>
>> does it related to change in the codebase or in a dependency/related
>> project ?
>>
>> I mean: is it something we have to fix/change in Beam ?
>>
>> Just curious as I'm not sure what you mean by "worker images" ;)
>>
>> Thanks !
>> Regards
>> JB
>>
>> On 31/01/2018 22:18, Alan Myrvold wrote:
>>
>> -1 (for now, hope to change this)
>>
>> Dataflow runner jobs are failing for me with 2.3.0 RC1, for both
>> Java and Python.
>>
>> This is not an issues with the 2.3.0 RC1 SDK, we (google) need
>> to release worker images.
>>
>> I have assigned these bugs to myself, and will be working to
>> help get these workers released.
>>
>> [BEAM-3584] Java dataflow job fails with 2.3.0 RC1, due to
>> missing worker image
>> [BEAM-3585] Python dataflow job fails with 2.3.0 RC1, due to
>> missing worker image
>>
>> On Wed, Jan 31, 2018 at 6:12 AM, Jean-Baptiste Onofré
>> 
>> >> wrote:
>>
>>  Thanks Kenn,
>>
>>  I prepared the list of tasks I did. I will complete where
>> release is
>>  out.
>>
>>  Regards
>>  JB
>>
>>  On 01/31/2018 03:07 PM, Kenneth Knowles wrote:
>>  > I've cloned the release validation spreadsheet:
>>  >
>>  > https://s.apache.org/beam-2.3.0-release-validation
>> 
>>  > >
>>  >
>>  > If you plan to perform a manual validation task, please
>> sign up so multiple
>>  > people don't waste effort.
>>  >
>>  > Alan & JB, as far as your pairing up to automate more,
>> anything manual on this
>>  > sheet should be considered.
>>  >
>>  > Kenn
>>  >
>>  > On Wed, Jan 31, 2018 at 5:59 AM, Jean-Baptiste Onofré
>> 
>> >
>>  > 
>> >  >
>>  > +1 (binding)
>>  >
>>  > Casting my own +1 ;)
>>  >
>>  > Regards
>>  > JB
>>  >
>>  > On 01/30/2018 09:04 AM, Jean-Baptiste Onofré wrote:
>>  > > Hi everyone,
>>  > >
>>  > > Please review and vote on the release candidate #1
>> for the version 2.3.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 to be deployed
>> to dist.apache.org  <
>> http://dist.apache.org>
>>   >  [2],
>>  > > which is signed with the key with fingerprint
>> C8282E76 [3],
>>  > > * all artifacts to be deployed to the Maven Central
>> Repository [4],
>>  > > * source code tag "v2.3.0-RC1" [5],
>>  > > * website pull request listing the release and
>> publishing the API reference
>>  > > manual [6].
>>  

Re: [VOTE] Release 2.3.0, release candidate #1

[Jean-Baptiste Onofré]

OK, I think I understood ;)

So it's not "directly" related to Beam itself (it's more a Dataflow step 
to perform).


@Alan, I think it's better to test first and then cast the vote. This 
kind of tests are valuable to validate the release and make sense. But 
vote should represent the state of the Beam release. So I think -1 vote 
is a bit too early before the test.


Thanks !
Regards
JB

On 31/01/2018 22:33, Reuven Lax wrote:
It's just a step that needs to be peformed before the new release works 
on Dataflow. Alan is saying that we've been unable to validate Dataflow 
so far, as worker images are not yet built. Hopefully they'll be built 
soon, and we'll be able to validate.


On Wed, Jan 31, 2018 at 1:31 PM, Jean-Baptiste Onofré > wrote:


Hi Alan

does it related to change in the codebase or in a dependency/related
project ?

I mean: is it something we have to fix/change in Beam ?

Just curious as I'm not sure what you mean by "worker images" ;)

Thanks !
Regards
JB

On 31/01/2018 22:18, Alan Myrvold wrote:

-1 (for now, hope to change this)

Dataflow runner jobs are failing for me with 2.3.0 RC1, for both
Java and Python.

This is not an issues with the 2.3.0 RC1 SDK, we (google) need
to release worker images.

I have assigned these bugs to myself, and will be working to
help get these workers released.

[BEAM-3584] Java dataflow job fails with 2.3.0 RC1, due to
missing worker image
[BEAM-3585] Python dataflow job fails with 2.3.0 RC1, due to
missing worker image

On Wed, Jan 31, 2018 at 6:12 AM, Jean-Baptiste Onofré

>> wrote:

     Thanks Kenn,

     I prepared the list of tasks I did. I will complete where
release is
     out.

     Regards
     JB

     On 01/31/2018 03:07 PM, Kenneth Knowles wrote:
     > I've cloned the release validation spreadsheet:
     >
     > https://s.apache.org/beam-2.3.0-release-validation

     >
     >
     > If you plan to perform a manual validation task, please
sign up so multiple
     > people don't waste effort.
     >
     > Alan & JB, as far as your pairing up to automate more,
anything manual on this
     > sheet should be considered.
     >
     > Kenn
     >
     > On Wed, Jan 31, 2018 at 5:59 AM, Jean-Baptiste Onofré

>
     > 

     >     +1 (binding)
     >
     >     Casting my own +1 ;)
     >
     >     Regards
     >     JB
     >
     >     On 01/30/2018 09:04 AM, Jean-Baptiste Onofré wrote:
     >     > Hi everyone,
     >     >
     >     > Please review and vote on the release candidate #1
for the version 2.3.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 to be deployed
to dist.apache.org  
      >      [2],
     >     > which is signed with the key with fingerprint
C8282E76 [3],
     >     > * all artifacts to be deployed to the Maven Central
Repository [4],
     >     > * source code tag "v2.3.0-RC1" [5],
     >     > * website pull request listing the release and
publishing the API reference
     >     > manual [6].
     >     > * Java artifacts were built with Maven 3.3.9 and
Oracle JDK 1.8.0_111.
     >     > * Python artifacts are deployed along with the
source release to the
      >     > dist.apache.org 

      [2].
     >     >
     >     > The vote will be open for at least 72 hours. It is
adopted by majority
     >     approval,
     >     

Re: [VOTE] Release 2.3.0, release candidate #1

[Reuven Lax]

It's just a step that needs to be peformed before the new release works on
Dataflow. Alan is saying that we've been unable to validate Dataflow so
far, as worker images are not yet built. Hopefully they'll be built soon,
and we'll be able to validate.

On Wed, Jan 31, 2018 at 1:31 PM, Jean-Baptiste Onofré 
wrote:

> Hi Alan
>
> does it related to change in the codebase or in a dependency/related
> project ?
>
> I mean: is it something we have to fix/change in Beam ?
>
> Just curious as I'm not sure what you mean by "worker images" ;)
>
> Thanks !
> Regards
> JB
>
> On 31/01/2018 22:18, Alan Myrvold wrote:
>
>> -1 (for now, hope to change this)
>>
>> Dataflow runner jobs are failing for me with 2.3.0 RC1, for both Java and
>> Python.
>>
>> This is not an issues with the 2.3.0 RC1 SDK, we (google) need to release
>> worker images.
>>
>> I have assigned these bugs to myself, and will be working to help get
>> these workers released.
>>
>> [BEAM-3584] Java dataflow job fails with 2.3.0 RC1, due to missing worker
>> image
>> [BEAM-3585] Python dataflow job fails with 2.3.0 RC1, due to missing
>> worker image
>>
>> On Wed, Jan 31, 2018 at 6:12 AM, Jean-Baptiste Onofré > > wrote:
>>
>> Thanks Kenn,
>>
>> I prepared the list of tasks I did. I will complete where release is
>> out.
>>
>> Regards
>> JB
>>
>> On 01/31/2018 03:07 PM, Kenneth Knowles wrote:
>> > I've cloned the release validation spreadsheet:
>> >
>> > https://s.apache.org/beam-2.3.0-release-validation
>> 
>> >
>> > If you plan to perform a manual validation task, please sign up so
>> multiple
>> > people don't waste effort.
>> >
>> > Alan & JB, as far as your pairing up to automate more, anything
>> manual on this
>> > sheet should be considered.
>> >
>> > Kenn
>> >
>> > On Wed, Jan 31, 2018 at 5:59 AM, Jean-Baptiste Onofré <
>> j...@nanthrax.net 
>> > >> wrote:
>> >
>> > +1 (binding)
>> >
>> > Casting my own +1 ;)
>> >
>> > Regards
>> > JB
>> >
>> > On 01/30/2018 09:04 AM, Jean-Baptiste Onofré wrote:
>> > > Hi everyone,
>> > >
>> > > Please review and vote on the release candidate #1 for the
>> version 2.3.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 to be deployed to
>> dist.apache.org 
>>  >  [2],
>> > > which is signed with the key with fingerprint C8282E76 [3],
>> > > * all artifacts to be deployed to the Maven Central
>> Repository [4],
>> > > * source code tag "v2.3.0-RC1" [5],
>> > > * website pull request listing the release and publishing the
>> API reference
>> > > manual [6].
>> > > * Java artifacts were built with Maven 3.3.9 and Oracle JDK
>> 1.8.0_111.
>> > > * Python artifacts are deployed along with the source release
>> to the
>>  > > dist.apache.org 
>>  [2].
>> > >
>> > > The vote will be open for at least 72 hours. It is adopted by
>> majority
>> > approval,
>> > > with at least 3 PMC affirmative votes.
>> > >
>> > > Thanks,
>> > > JB
>> > >
>> > > [1]
>> > >
>> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?proj
>> ectId=12319527=12341608
>> > ectId=12319527=12341608>
>> > > jectId=12319527=12341608
>> > ectId=12319527=12341608>>
>> > > [2] https://dist.apache.org/repos/dist/dev/beam/2.3.0/
>> 
>> > > >
>> > > [3] https://dist.apache.org/repos/dist/release/beam/KEYS
>> 
>> > > >
>> > > [4] https://repository.apache.org/
>> content/repositories/orgapachebeam-1026/
>> > ebeam-1026/>
>> > 

Re: [VOTE] Release 2.3.0, release candidate #1

[Jean-Baptiste Onofré]

Hi Alan

does it related to change in the codebase or in a dependency/related 
project ?


I mean: is it something we have to fix/change in Beam ?

Just curious as I'm not sure what you mean by "worker images" ;)

Thanks !
Regards
JB

On 31/01/2018 22:18, Alan Myrvold wrote:

-1 (for now, hope to change this)

Dataflow runner jobs are failing for me with 2.3.0 RC1, for both Java 
and Python.


This is not an issues with the 2.3.0 RC1 SDK, we (google) need to 
release worker images.


I have assigned these bugs to myself, and will be working to help get 
these workers released.


[BEAM-3584] Java dataflow job fails with 2.3.0 RC1, due to missing 
worker image
[BEAM-3585] Python dataflow job fails with 2.3.0 RC1, due to missing 
worker image


On Wed, Jan 31, 2018 at 6:12 AM, Jean-Baptiste Onofré > wrote:


Thanks Kenn,

I prepared the list of tasks I did. I will complete where release is
out.

Regards
JB

On 01/31/2018 03:07 PM, Kenneth Knowles wrote:
> I've cloned the release validation spreadsheet:
>
> https://s.apache.org/beam-2.3.0-release-validation

>
> If you plan to perform a manual validation task, please sign up so 
multiple
> people don't waste effort.
>
> Alan & JB, as far as your pairing up to automate more, anything manual on 
this
> sheet should be considered.
>
> Kenn
>
> On Wed, Jan 31, 2018 at 5:59 AM, Jean-Baptiste Onofré 
> >> wrote:
>
>     +1 (binding)
>
>     Casting my own +1 ;)
>
>     Regards
>     JB
>
>     On 01/30/2018 09:04 AM, Jean-Baptiste Onofré wrote:
>     > Hi everyone,
>     >
>     > Please review and vote on the release candidate #1 for the version 
2.3.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 to be deployed to dist.apache.org 

 >      [2],
>     > which is signed with the key with fingerprint C8282E76 [3],
>     > * all artifacts to be deployed to the Maven Central Repository [4],
>     > * source code tag "v2.3.0-RC1" [5],
>     > * website pull request listing the release and publishing the API 
reference
>     > manual [6].
>     > * Java artifacts were built with Maven 3.3.9 and Oracle JDK 
1.8.0_111.
>     > * Python artifacts are deployed along with the source release to the
 >     > dist.apache.org 
 [2].
>     >
>     > The vote will be open for at least 72 hours. It is adopted by 
majority
>     approval,
>     > with at least 3 PMC affirmative votes.
>     >
>     > Thanks,
>     > JB
>     >
>     > [1]
>     >
> 
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527=12341608


>     
>
>     > [2] https://dist.apache.org/repos/dist/dev/beam/2.3.0/

>     >
>     > [3] https://dist.apache.org/repos/dist/release/beam/KEYS

>     >
>     > [4] 
https://repository.apache.org/content/repositories/orgapachebeam-1026/

>     
>
>     > [5] https://github.com/apache/beam/tree/v2.3.0-RC1

>     >
>     > [6] https://github.com/apache/beam-site/pull/381

>     >
>     >
>
>     --
>     Jean-Baptiste Onofré
 > jbono...@apache.org 

Re: [VOTE] Release 2.3.0, release candidate #1

[Alan Myrvold]

-1 (for now, hope to change this)

Dataflow runner jobs are failing for me with 2.3.0 RC1, for both Java and
Python.

This is not an issues with the 2.3.0 RC1 SDK, we (google) need to release
worker images.

I have assigned these bugs to myself, and will be working to help get these
workers released.

[BEAM-3584] Java dataflow job fails with 2.3.0 RC1, due to missing worker
image
[BEAM-3585] Python dataflow job fails with 2.3.0 RC1, due to missing worker
image

On Wed, Jan 31, 2018 at 6:12 AM, Jean-Baptiste Onofré 
wrote:

> Thanks Kenn,
>
> I prepared the list of tasks I did. I will complete where release is out.
>
> Regards
> JB
>
> On 01/31/2018 03:07 PM, Kenneth Knowles wrote:
> > I've cloned the release validation spreadsheet:
> >
> > https://s.apache.org/beam-2.3.0-release-validation
> >
> > If you plan to perform a manual validation task, please sign up so
> multiple
> > people don't waste effort.
> >
> > Alan & JB, as far as your pairing up to automate more, anything manual
> on this
> > sheet should be considered.
> >
> > Kenn
> >
> > On Wed, Jan 31, 2018 at 5:59 AM, Jean-Baptiste Onofré  > > wrote:
> >
> > +1 (binding)
> >
> > Casting my own +1 ;)
> >
> > Regards
> > JB
> >
> > On 01/30/2018 09:04 AM, Jean-Baptiste Onofré wrote:
> > > Hi everyone,
> > >
> > > Please review and vote on the release candidate #1 for the version
> 2.3.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 to be deployed to
> dist.apache.org
> >  [2],
> > > which is signed with the key with fingerprint C8282E76 [3],
> > > * all artifacts to be deployed to the Maven Central Repository [4],
> > > * source code tag "v2.3.0-RC1" [5],
> > > * website pull request listing the release and publishing the API
> reference
> > > manual [6].
> > > * Java artifacts were built with Maven 3.3.9 and Oracle JDK
> 1.8.0_111.
> > > * Python artifacts are deployed along with the source release to
> the
> > > dist.apache.org  [2].
> > >
> > > The vote will be open for at least 72 hours. It is adopted by
> majority
> > approval,
> > > with at least 3 PMC affirmative votes.
> > >
> > > Thanks,
> > > JB
> > >
> > > [1]
> > >
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12319527=12341608
> >  projectId=12319527=12341608>
> > > [2] https://dist.apache.org/repos/dist/dev/beam/2.3.0/
> > 
> > > [3] https://dist.apache.org/repos/dist/release/beam/KEYS
> > 
> > > [4] https://repository.apache.org/content/repositories/
> orgapachebeam-1026/
> >  orgapachebeam-1026/>
> > > [5] https://github.com/apache/beam/tree/v2.3.0-RC1
> > 
> > > [6] https://github.com/apache/beam-site/pull/381
> > 
> > >
> >
> > --
> > Jean-Baptiste Onofré
> > jbono...@apache.org 
> > http://blog.nanthrax.net
> > Talend - http://www.talend.com
> >
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: [VOTE] Release 2.3.0, release candidate #1

[Jean-Baptiste Onofré]

Thanks Kenn,

I prepared the list of tasks I did. I will complete where release is out.

Regards
JB

On 01/31/2018 03:07 PM, Kenneth Knowles wrote:
> I've cloned the release validation spreadsheet:
> 
>     https://s.apache.org/beam-2.3.0-release-validation
> 
> If you plan to perform a manual validation task, please sign up so multiple
> people don't waste effort.
> 
> Alan & JB, as far as your pairing up to automate more, anything manual on this
> sheet should be considered.
> 
> Kenn
> 
> On Wed, Jan 31, 2018 at 5:59 AM, Jean-Baptiste Onofré  > wrote:
> 
> +1 (binding)
> 
> Casting my own +1 ;)
> 
> Regards
> JB
> 
> On 01/30/2018 09:04 AM, Jean-Baptiste Onofré wrote:
> > Hi everyone,
> >
> > Please review and vote on the release candidate #1 for the version 
> 2.3.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 to be deployed to dist.apache.org
>  [2],
> > which is signed with the key with fingerprint C8282E76 [3],
> > * all artifacts to be deployed to the Maven Central Repository [4],
> > * source code tag "v2.3.0-RC1" [5],
> > * website pull request listing the release and publishing the API 
> reference
> > manual [6].
> > * Java artifacts were built with Maven 3.3.9 and Oracle JDK 1.8.0_111.
> > * Python artifacts are deployed along with the source release to the
> > dist.apache.org  [2].
> >
> > The vote will be open for at least 72 hours. It is adopted by majority
> approval,
> > with at least 3 PMC affirmative votes.
> >
> > Thanks,
> > JB
> >
> > [1]
> >
> 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527=12341608
> 
> 
> > [2] https://dist.apache.org/repos/dist/dev/beam/2.3.0/
> 
> > [3] https://dist.apache.org/repos/dist/release/beam/KEYS
> 
> > [4] 
> https://repository.apache.org/content/repositories/orgapachebeam-1026/
> 
> > [5] https://github.com/apache/beam/tree/v2.3.0-RC1
> 
> > [6] https://github.com/apache/beam-site/pull/381
> 
> >
> 
> --
> Jean-Baptiste Onofré
> jbono...@apache.org 
> http://blog.nanthrax.net
> Talend - http://www.talend.com
> 
> 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [VOTE] Release 2.3.0, release candidate #1

[Kenneth Knowles]

I've cloned the release validation spreadsheet:

https://s.apache.org/beam-2.3.0-release-validation

If you plan to perform a manual validation task, please sign up so multiple
people don't waste effort.

Alan & JB, as far as your pairing up to automate more, anything manual on
this sheet should be considered.

Kenn

On Wed, Jan 31, 2018 at 5:59 AM, Jean-Baptiste Onofré 
wrote:

> +1 (binding)
>
> Casting my own +1 ;)
>
> Regards
> JB
>
> On 01/30/2018 09:04 AM, Jean-Baptiste Onofré wrote:
> > Hi everyone,
> >
> > Please review and vote on the release candidate #1 for the version
> 2.3.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 to be deployed to dist.apache.org
> [2],
> > which is signed with the key with fingerprint C8282E76 [3],
> > * all artifacts to be deployed to the Maven Central Repository [4],
> > * source code tag "v2.3.0-RC1" [5],
> > * website pull request listing the release and publishing the API
> reference
> > manual [6].
> > * Java artifacts were built with Maven 3.3.9 and Oracle JDK 1.8.0_111.
> > * Python artifacts are deployed along with the source release to the
> > dist.apache.org [2].
> >
> > The vote will be open for at least 72 hours. It is adopted by majority
> approval,
> > with at least 3 PMC affirmative votes.
> >
> > Thanks,
> > JB
> >
> > [1]
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12319527=12341608
> > [2] https://dist.apache.org/repos/dist/dev/beam/2.3.0/
> > [3] https://dist.apache.org/repos/dist/release/beam/KEYS
> > [4] https://repository.apache.org/content/repositories/
> orgapachebeam-1026/
> > [5] https://github.com/apache/beam/tree/v2.3.0-RC1
> > [6] https://github.com/apache/beam-site/pull/381
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: [VOTE] Release 2.3.0, release candidate #1

[Jean-Baptiste Onofré]

+1 (binding)

Casting my own +1 ;)

Regards
JB

On 01/30/2018 09:04 AM, Jean-Baptiste Onofré wrote:
> Hi everyone,
> 
> Please review and vote on the release candidate #1 for the version 2.3.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 to be deployed to dist.apache.org [2],
> which is signed with the key with fingerprint C8282E76 [3],
> * all artifacts to be deployed to the Maven Central Repository [4],
> * source code tag "v2.3.0-RC1" [5],
> * website pull request listing the release and publishing the API reference
> manual [6].
> * Java artifacts were built with Maven 3.3.9 and Oracle JDK 1.8.0_111.
> * Python artifacts are deployed along with the source release to the
> dist.apache.org [2].
> 
> The vote will be open for at least 72 hours. It is adopted by majority 
> approval,
> with at least 3 PMC affirmative votes.
> 
> Thanks,
> JB
> 
> [1]
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527=12341608
> [2] https://dist.apache.org/repos/dist/dev/beam/2.3.0/
> [3] https://dist.apache.org/repos/dist/release/beam/KEYS
> [4] https://repository.apache.org/content/repositories/orgapachebeam-1026/
> [5] https://github.com/apache/beam/tree/v2.3.0-RC1
> [6] https://github.com/apache/beam-site/pull/381
> 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com