[VOTE] Release 2.11.0, release candidate #2

[Ahmet Altay]

Hi everyone,

Please review and vote on the release candidate #2 for the version 2.11.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
64B84A5AD91F9C20F5E9D9A7D62E71416096FA00 [3],
* all artifacts to be deployed to the Maven Central Repository [4],
* source code tag "v2.11.0-RC2" [5],
* website pull request listing the release [6] and publishing the API
reference manual [7].
* Python artifacts are deployed along with the source release to the
dist.apache.org [2].
* Validation sheet with a tab for 2.11.0 release to help with validation
[8].

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

Thanks,
Ahmet

[1]
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527&version=12344775
[2] https://dist.apache.org/repos/dist/dev/beam/2.11.0/
[3] https://dist.apache.org/repos/dist/release/beam/KEYS
[4] https://repository.apache.org/content/repositories/orgapachebeam-1064/
[5] https://github.com/apache/beam/tree/v2.11.0-RC2
[6] https://github.com/apache/beam/pull/7924
[7] https://github.com/apache/beam-site/pull/587
[8]
https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=542393513

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

[Maximilian Michels]

+1 (binding)

* Verified checksums
* Ran quickstart WordCount tests local/cluster with the Flink Runner

-Max

On 26.02.19 10:40, Ahmet Altay wrote:

Hi everyone,

Please review and vote on the release candidate #2 for the version 
2.11.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 64B84A5AD91F9C20F5E9D9A7D62E71416096FA00 [3],

* all artifacts to be deployed to the Maven Central Repository [4],
* source code tag "v2.11.0-RC2" [5],
* website pull request listing the release [6] and publishing the API 
reference manual [7].
* Python artifacts are deployed along with the source release to the 
dist.apache.org  [2].
* Validation sheet with a tab for 2.11.0 release to help with validation 
[8].


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


Thanks,
Ahmet

[1] 
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527&version=12344775

[2] https://dist.apache.org/repos/dist/dev/beam/2.11.0/
[3] https://dist.apache.org/repos/dist/release/beam/KEYS
[4] https://repository.apache.org/content/repositories/orgapachebeam-1064/
[5] https://github.com/apache/beam/tree/v2.11.0-RC2
[6] https://github.com/apache/beam/pull/7924
[7] https://github.com/apache/beam-site/pull/587
[8] 
https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=542393513

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

[Konstantinos Katsiapis]

+1.
(Same rational as my earlier post for RC1).

On Tue, Feb 26, 2019 at 2:19 AM Maximilian Michels  wrote:

> +1 (binding)
>
> * Verified checksums
> * Ran quickstart WordCount tests local/cluster with the Flink Runner
>
> -Max
>
> On 26.02.19 10:40, Ahmet Altay wrote:
> > Hi everyone,
> >
> > Please review and vote on the release candidate #2 for the version
> > 2.11.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 64B84A5AD91F9C20F5E9D9A7D62E71416096FA00 [3],
> > * all artifacts to be deployed to the Maven Central Repository [4],
> > * source code tag "v2.11.0-RC2" [5],
> > * website pull request listing the release [6] and publishing the API
> > reference manual [7].
> > * Python artifacts are deployed along with the source release to the
> > dist.apache.org  [2].
> > * Validation sheet with a tab for 2.11.0 release to help with validation
> > [8].
> >
> > The vote will be open for at least 72 hours. It is adopted by majority
> > approval, with at least 3 PMC affirmative votes.
> >
> > Thanks,
> > Ahmet
> >
> > [1]
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527&version=12344775
> > [2] https://dist.apache.org/repos/dist/dev/beam/2.11.0/
> > [3] https://dist.apache.org/repos/dist/release/beam/KEYS
> > [4]
> https://repository.apache.org/content/repositories/orgapachebeam-1064/
> > [5] https://github.com/apache/beam/tree/v2.11.0-RC2
> > [6] https://github.com/apache/beam/pull/7924
> > [7] https://github.com/apache/beam-site/pull/587
> > [8]
> >
> https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=542393513
> >
>


-- 
Gus Katsiapis | Software Engineer | katsia...@google.com | 650-918-7487

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

[Charles Chen]

Thank you, +1.  I tested Python 3 support in batch and streaming mode
(using wordcount and streaming wordcount) on both DirectRunner and
DataflowRunner.

On Tue, Feb 26, 2019 at 7:54 AM Konstantinos Katsiapis 
wrote:

> +1.
> (Same rational as my earlier post for RC1).
>
> On Tue, Feb 26, 2019 at 2:19 AM Maximilian Michels  wrote:
>
>> +1 (binding)
>>
>> * Verified checksums
>> * Ran quickstart WordCount tests local/cluster with the Flink Runner
>>
>> -Max
>>
>> On 26.02.19 10:40, Ahmet Altay wrote:
>> > Hi everyone,
>> >
>> > Please review and vote on the release candidate #2 for the version
>> > 2.11.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 64B84A5AD91F9C20F5E9D9A7D62E71416096FA00 [3],
>> > * all artifacts to be deployed to the Maven Central Repository [4],
>> > * source code tag "v2.11.0-RC2" [5],
>> > * website pull request listing the release [6] and publishing the API
>> > reference manual [7].
>> > * Python artifacts are deployed along with the source release to the
>> > dist.apache.org  [2].
>> > * Validation sheet with a tab for 2.11.0 release to help with
>> validation
>> > [8].
>> >
>> > The vote will be open for at least 72 hours. It is adopted by majority
>> > approval, with at least 3 PMC affirmative votes.
>> >
>> > Thanks,
>> > Ahmet
>> >
>> > [1]
>> >
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527&version=12344775
>> > [2] https://dist.apache.org/repos/dist/dev/beam/2.11.0/
>> > [3] https://dist.apache.org/repos/dist/release/beam/KEYS
>> > [4]
>> https://repository.apache.org/content/repositories/orgapachebeam-1064/
>> > [5] https://github.com/apache/beam/tree/v2.11.0-RC2
>> > [6] https://github.com/apache/beam/pull/7924
>> > [7] https://github.com/apache/beam-site/pull/587
>> > [8]
>> >
>> https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=542393513
>> >
>>
>
>
> --
> Gus Katsiapis | Software Engineer | katsia...@google.com | 650-918-7487
>

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

[Reuven Lax]

+1 (binding)

On Tue, Feb 26, 2019 at 2:16 PM Charles Chen  wrote:

> Thank you, +1.  I tested Python 3 support in batch and streaming mode
> (using wordcount and streaming wordcount) on both DirectRunner and
> DataflowRunner.
>
> On Tue, Feb 26, 2019 at 7:54 AM Konstantinos Katsiapis <
> katsia...@google.com> wrote:
>
>> +1.
>> (Same rational as my earlier post for RC1).
>>
>> On Tue, Feb 26, 2019 at 2:19 AM Maximilian Michels 
>> wrote:
>>
>>> +1 (binding)
>>>
>>> * Verified checksums
>>> * Ran quickstart WordCount tests local/cluster with the Flink Runner
>>>
>>> -Max
>>>
>>> On 26.02.19 10:40, Ahmet Altay wrote:
>>> > Hi everyone,
>>> >
>>> > Please review and vote on the release candidate #2 for the version
>>> > 2.11.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 64B84A5AD91F9C20F5E9D9A7D62E71416096FA00 [3],
>>> > * all artifacts to be deployed to the Maven Central Repository [4],
>>> > * source code tag "v2.11.0-RC2" [5],
>>> > * website pull request listing the release [6] and publishing the API
>>> > reference manual [7].
>>> > * Python artifacts are deployed along with the source release to the
>>> > dist.apache.org  [2].
>>> > * Validation sheet with a tab for 2.11.0 release to help with
>>> validation
>>> > [8].
>>> >
>>> > The vote will be open for at least 72 hours. It is adopted by majority
>>> > approval, with at least 3 PMC affirmative votes.
>>> >
>>> > Thanks,
>>> > Ahmet
>>> >
>>> > [1]
>>> >
>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527&version=12344775
>>> > [2] https://dist.apache.org/repos/dist/dev/beam/2.11.0/
>>> > [3] https://dist.apache.org/repos/dist/release/beam/KEYS
>>> > [4]
>>> https://repository.apache.org/content/repositories/orgapachebeam-1064/
>>> > [5] https://github.com/apache/beam/tree/v2.11.0-RC2
>>> > [6] https://github.com/apache/beam/pull/7924
>>> > [7] https://github.com/apache/beam-site/pull/587
>>> > [8]
>>> >
>>> https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=542393513
>>> >
>>>
>>
>>
>> --
>> Gus Katsiapis | Software Engineer | katsia...@google.com | 650-918-7487
>>
>

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

[Kenneth Knowles]

+1 (binding)

Ran run_rc_validation.sh and said "yes" to everything up to one mobile
gaming example. I did not get to the Python tests towards the end of the
script (it is the same as last RC anyhow? I did not verify this)

On Tue, Feb 26, 2019 at 2:16 PM Charles Chen  wrote:

> Thank you, +1.  I tested Python 3 support in batch and streaming mode
> (using wordcount and streaming wordcount) on both DirectRunner and
> DataflowRunner.
>
> On Tue, Feb 26, 2019 at 7:54 AM Konstantinos Katsiapis <
> katsia...@google.com> wrote:
>
>> +1.
>> (Same rational as my earlier post for RC1).
>>
>> On Tue, Feb 26, 2019 at 2:19 AM Maximilian Michels 
>> wrote:
>>
>>> +1 (binding)
>>>
>>> * Verified checksums
>>> * Ran quickstart WordCount tests local/cluster with the Flink Runner
>>>
>>> -Max
>>>
>>> On 26.02.19 10:40, Ahmet Altay wrote:
>>> > Hi everyone,
>>> >
>>> > Please review and vote on the release candidate #2 for the version
>>> > 2.11.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 64B84A5AD91F9C20F5E9D9A7D62E71416096FA00 [3],
>>> > * all artifacts to be deployed to the Maven Central Repository [4],
>>> > * source code tag "v2.11.0-RC2" [5],
>>> > * website pull request listing the release [6] and publishing the API
>>> > reference manual [7].
>>> > * Python artifacts are deployed along with the source release to the
>>> > dist.apache.org  [2].
>>> > * Validation sheet with a tab for 2.11.0 release to help with
>>> validation
>>> > [8].
>>> >
>>> > The vote will be open for at least 72 hours. It is adopted by majority
>>> > approval, with at least 3 PMC affirmative votes.
>>> >
>>> > Thanks,
>>> > Ahmet
>>> >
>>> > [1]
>>> >
>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527&version=12344775
>>> > [2] https://dist.apache.org/repos/dist/dev/beam/2.11.0/
>>> > [3] https://dist.apache.org/repos/dist/release/beam/KEYS
>>> > [4]
>>> https://repository.apache.org/content/repositories/orgapachebeam-1064/
>>> > [5] https://github.com/apache/beam/tree/v2.11.0-RC2
>>> > [6] https://github.com/apache/beam/pull/7924
>>> > [7] https://github.com/apache/beam-site/pull/587
>>> > [8]
>>> >
>>> https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=542393513
>>> >
>>>
>>
>>
>> --
>> Gus Katsiapis | Software Engineer | katsia...@google.com | 650-918-7487
>>
>

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

[Ahmet Altay]

+1 (binding)

On Tue, Feb 26, 2019 at 9:18 PM Kenneth Knowles  wrote:

> +1 (binding)
>
> Ran run_rc_validation.sh and said "yes" to everything up to one mobile
> gaming example. I did not get to the Python tests towards the end of the
> script (it is the same as last RC anyhow? I did not verify this)
>
> On Tue, Feb 26, 2019 at 2:16 PM Charles Chen  wrote:
>
>> Thank you, +1.  I tested Python 3 support in batch and streaming mode
>> (using wordcount and streaming wordcount) on both DirectRunner and
>> DataflowRunner.
>>
>> On Tue, Feb 26, 2019 at 7:54 AM Konstantinos Katsiapis <
>> katsia...@google.com> wrote:
>>
>>> +1.
>>> (Same rational as my earlier post for RC1).
>>>
>>> On Tue, Feb 26, 2019 at 2:19 AM Maximilian Michels 
>>> wrote:
>>>
 +1 (binding)

 * Verified checksums
 * Ran quickstart WordCount tests local/cluster with the Flink Runner

 -Max

 On 26.02.19 10:40, Ahmet Altay wrote:
 > Hi everyone,
 >
 > Please review and vote on the release candidate #2 for the version
 > 2.11.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 64B84A5AD91F9C20F5E9D9A7D62E71416096FA00 [3],
 > * all artifacts to be deployed to the Maven Central Repository [4],
 > * source code tag "v2.11.0-RC2" [5],
 > * website pull request listing the release [6] and publishing the API
 > reference manual [7].
 > * Python artifacts are deployed along with the source release to the
 > dist.apache.org  [2].
 > * Validation sheet with a tab for 2.11.0 release to help with
 validation
 > [8].
 >
 > The vote will be open for at least 72 hours. It is adopted by
 majority
 > approval, with at least 3 PMC affirmative votes.
 >
 > Thanks,
 > Ahmet
 >
 > [1]
 >
 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527&version=12344775
 > [2] https://dist.apache.org/repos/dist/dev/beam/2.11.0/
 > [3] https://dist.apache.org/repos/dist/release/beam/KEYS
 > [4]
 https://repository.apache.org/content/repositories/orgapachebeam-1064/
 > [5] https://github.com/apache/beam/tree/v2.11.0-RC2
 > [6] https://github.com/apache/beam/pull/7924
 > [7] https://github.com/apache/beam-site/pull/587
 > [8]
 >
 https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=542393513
 >

>>>
>>>
>>> --
>>> Gus Katsiapis | Software Engineer | katsia...@google.com | 650-918-7487
>>>
>>

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

[Ahmet Altay]

Thank you everyone for voting.

The vote has passed with 5 supportive +1 votes, 4 of which are binding PMC
votes:

* Maximilian Michels
* Reuven Lax
* Kenneth Knowles
* Ahmet Altay

I will proceed with release finalization steps.

Ahmet

On Fri, Mar 1, 2019 at 6:59 AM Ahmet Altay  wrote:

> +1 (binding)
>
> On Tue, Feb 26, 2019 at 9:18 PM Kenneth Knowles  wrote:
>
>> +1 (binding)
>>
>> Ran run_rc_validation.sh and said "yes" to everything up to one mobile
>> gaming example. I did not get to the Python tests towards the end of the
>> script (it is the same as last RC anyhow? I did not verify this)
>>
>> On Tue, Feb 26, 2019 at 2:16 PM Charles Chen  wrote:
>>
>>> Thank you, +1.  I tested Python 3 support in batch and streaming mode
>>> (using wordcount and streaming wordcount) on both DirectRunner and
>>> DataflowRunner.
>>>
>>> On Tue, Feb 26, 2019 at 7:54 AM Konstantinos Katsiapis <
>>> katsia...@google.com> wrote:
>>>
 +1.
 (Same rational as my earlier post for RC1).

 On Tue, Feb 26, 2019 at 2:19 AM Maximilian Michels 
 wrote:

> +1 (binding)
>
> * Verified checksums
> * Ran quickstart WordCount tests local/cluster with the Flink Runner
>
> -Max
>
> On 26.02.19 10:40, Ahmet Altay wrote:
> > Hi everyone,
> >
> > Please review and vote on the release candidate #2 for the version
> > 2.11.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 64B84A5AD91F9C20F5E9D9A7D62E71416096FA00 [3],
> > * all artifacts to be deployed to the Maven Central Repository [4],
> > * source code tag "v2.11.0-RC2" [5],
> > * website pull request listing the release [6] and publishing the
> API
> > reference manual [7].
> > * Python artifacts are deployed along with the source release to the
> > dist.apache.org  [2].
> > * Validation sheet with a tab for 2.11.0 release to help with
> validation
> > [8].
> >
> > The vote will be open for at least 72 hours. It is adopted by
> majority
> > approval, with at least 3 PMC affirmative votes.
> >
> > Thanks,
> > Ahmet
> >
> > [1]
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527&version=12344775
> > [2] https://dist.apache.org/repos/dist/dev/beam/2.11.0/
> > [3] https://dist.apache.org/repos/dist/release/beam/KEYS
> > [4]
> https://repository.apache.org/content/repositories/orgapachebeam-1064/
> > [5] https://github.com/apache/beam/tree/v2.11.0-RC2
> > [6] https://github.com/apache/beam/pull/7924
> > [7] https://github.com/apache/beam-site/pull/587
> > [8]
> >
> https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=542393513
> >
>


 --
 Gus Katsiapis | Software Engineer | katsia...@google.com | 650-918-7487

>>>

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

[Connell O'Callaghan]

Excellent thank you Ahmet and all involved!!!

On Fri, Mar 1, 2019, 7:23 AM Ahmet Altay  wrote:

> Thank you everyone for voting.
>
> The vote has passed with 5 supportive +1 votes, 4 of which are binding PMC
> votes:
>
> * Maximilian Michels
> * Reuven Lax
> * Kenneth Knowles
> * Ahmet Altay
>
> I will proceed with release finalization steps.
>
> Ahmet
>
> On Fri, Mar 1, 2019 at 6:59 AM Ahmet Altay  wrote:
>
>> +1 (binding)
>>
>> On Tue, Feb 26, 2019 at 9:18 PM Kenneth Knowles  wrote:
>>
>>> +1 (binding)
>>>
>>> Ran run_rc_validation.sh and said "yes" to everything up to one mobile
>>> gaming example. I did not get to the Python tests towards the end of the
>>> script (it is the same as last RC anyhow? I did not verify this)
>>>
>>> On Tue, Feb 26, 2019 at 2:16 PM Charles Chen  wrote:
>>>
 Thank you, +1.  I tested Python 3 support in batch and streaming mode
 (using wordcount and streaming wordcount) on both DirectRunner and
 DataflowRunner.

 On Tue, Feb 26, 2019 at 7:54 AM Konstantinos Katsiapis <
 katsia...@google.com> wrote:

> +1.
> (Same rational as my earlier post for RC1).
>
> On Tue, Feb 26, 2019 at 2:19 AM Maximilian Michels 
> wrote:
>
>> +1 (binding)
>>
>> * Verified checksums
>> * Ran quickstart WordCount tests local/cluster with the Flink Runner
>>
>> -Max
>>
>> On 26.02.19 10:40, Ahmet Altay wrote:
>> > Hi everyone,
>> >
>> > Please review and vote on the release candidate #2 for the version
>> > 2.11.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 64B84A5AD91F9C20F5E9D9A7D62E71416096FA00 [3],
>> > * all artifacts to be deployed to the Maven Central Repository [4],
>> > * source code tag "v2.11.0-RC2" [5],
>> > * website pull request listing the release [6] and publishing the
>> API
>> > reference manual [7].
>> > * Python artifacts are deployed along with the source release to
>> the
>> > dist.apache.org  [2].
>> > * Validation sheet with a tab for 2.11.0 release to help with
>> validation
>> > [8].
>> >
>> > The vote will be open for at least 72 hours. It is adopted by
>> majority
>> > approval, with at least 3 PMC affirmative votes.
>> >
>> > Thanks,
>> > Ahmet
>> >
>> > [1]
>> >
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527&version=12344775
>> > [2] https://dist.apache.org/repos/dist/dev/beam/2.11.0/
>> > [3] https://dist.apache.org/repos/dist/release/beam/KEYS
>> > [4]
>> https://repository.apache.org/content/repositories/orgapachebeam-1064/
>> > [5] https://github.com/apache/beam/tree/v2.11.0-RC2
>> > [6] https://github.com/apache/beam/pull/7924
>> > [7] https://github.com/apache/beam-site/pull/587
>> > [8]
>> >
>> https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=542393513
>> >
>>
>
>
> --
> Gus Katsiapis | Software Engineer | katsia...@google.com |
>  650-918-7487
>

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

[Jean-Baptiste Onofré]

+1 (binding)

Tested with beam-samples.

Regards
JB

On 26/02/2019 10:40, Ahmet Altay wrote:
> Hi everyone,
> 
> Please review and vote on the release candidate #2 for the version
> 2.11.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 64B84A5AD91F9C20F5E9D9A7D62E71416096FA00 [3],
> * all artifacts to be deployed to the Maven Central Repository [4],
> * source code tag "v2.11.0-RC2" [5],
> * website pull request listing the release [6] and publishing the API
> reference manual [7].
> * Python artifacts are deployed along with the source release to the
> dist.apache.org  [2].
> * Validation sheet with a tab for 2.11.0 release to help with validation
> [8].
> 
> The vote will be open for at least 72 hours. It is adopted by majority
> approval, with at least 3 PMC affirmative votes.
> 
> Thanks,
> Ahmet
> 
> [1]
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527&version=12344775
> [2] https://dist.apache.org/repos/dist/dev/beam/2.11.0/
> [3] https://dist.apache.org/repos/dist/release/beam/KEYS
> [4] https://repository.apache.org/content/repositories/orgapachebeam-1064/
> [5] https://github.com/apache/beam/tree/v2.11.0-RC2
> [6] https://github.com/apache/beam/pull/7924
> [7] https://github.com/apache/beam-site/pull/587
> [8]
> https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=542393513
> 

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

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

[Robert Bradshaw]

I see the vote has passed, but +1 (binding) from me as well.

On Mon, Mar 4, 2019 at 11:51 AM Jean-Baptiste Onofré  wrote:
>
> +1 (binding)
>
> Tested with beam-samples.
>
> Regards
> JB
>
> On 26/02/2019 10:40, Ahmet Altay wrote:
> > Hi everyone,
> >
> > Please review and vote on the release candidate #2 for the version
> > 2.11.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 64B84A5AD91F9C20F5E9D9A7D62E71416096FA00 [3],
> > * all artifacts to be deployed to the Maven Central Repository [4],
> > * source code tag "v2.11.0-RC2" [5],
> > * website pull request listing the release [6] and publishing the API
> > reference manual [7].
> > * Python artifacts are deployed along with the source release to the
> > dist.apache.org  [2].
> > * Validation sheet with a tab for 2.11.0 release to help with validation
> > [8].
> >
> > The vote will be open for at least 72 hours. It is adopted by majority
> > approval, with at least 3 PMC affirmative votes.
> >
> > Thanks,
> > Ahmet
> >
> > [1]
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527&version=12344775
> > [2] https://dist.apache.org/repos/dist/dev/beam/2.11.0/
> > [3] https://dist.apache.org/repos/dist/release/beam/KEYS
> > [4] https://repository.apache.org/content/repositories/orgapachebeam-1064/
> > [5] https://github.com/apache/beam/tree/v2.11.0-RC2
> > [6] https://github.com/apache/beam/pull/7924
> > [7] https://github.com/apache/beam-site/pull/587
> > [8]
> > https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=542393513
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com

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

[Ahmet Altay]

Thank you for the additional votes and validations.

Update: Binaries are pushed. Website updates are blocked on an issue that
is preventing beam-site changes to be synced the beam website.
(INFRA-17953). I am waiting for that to be resolved before sending an
announcement.

On Mon, Mar 4, 2019 at 3:00 AM Robert Bradshaw  wrote:

> I see the vote has passed, but +1 (binding) from me as well.
>
> On Mon, Mar 4, 2019 at 11:51 AM Jean-Baptiste Onofré 
> wrote:
> >
> > +1 (binding)
> >
> > Tested with beam-samples.
> >
> > Regards
> > JB
> >
> > On 26/02/2019 10:40, Ahmet Altay wrote:
> > > Hi everyone,
> > >
> > > Please review and vote on the release candidate #2 for the version
> > > 2.11.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 64B84A5AD91F9C20F5E9D9A7D62E71416096FA00 [3],
> > > * all artifacts to be deployed to the Maven Central Repository [4],
> > > * source code tag "v2.11.0-RC2" [5],
> > > * website pull request listing the release [6] and publishing the API
> > > reference manual [7].
> > > * Python artifacts are deployed along with the source release to the
> > > dist.apache.org  [2].
> > > * Validation sheet with a tab for 2.11.0 release to help with
> validation
> > > [8].
> > >
> > > The vote will be open for at least 72 hours. It is adopted by majority
> > > approval, with at least 3 PMC affirmative votes.
> > >
> > > Thanks,
> > > Ahmet
> > >
> > > [1]
> > >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527&version=12344775
> > > [2] https://dist.apache.org/repos/dist/dev/beam/2.11.0/
> > > [3] https://dist.apache.org/repos/dist/release/beam/KEYS
> > > [4]
> https://repository.apache.org/content/repositories/orgapachebeam-1064/
> > > [5] https://github.com/apache/beam/tree/v2.11.0-RC2
> > > [6] https://github.com/apache/beam/pull/7924
> > > [7] https://github.com/apache/beam-site/pull/587
> > > [8]
> > >
> https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=542393513
> > >
> >
> > --
> > Jean-Baptiste Onofré
> > jbono...@apache.org
> > http://blog.nanthrax.net
> > Talend - http://www.talend.com
>

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

[Etienne Chauchot]

@Ahmet sorry I did not have time to check 2.11 release but a fellow Beam 
contributor drew my attention on something:
the 2.11 release tag points on commit of 02/26 and this[1] PR was merged 02/20 
and that [2] PR was merged on 02/18. So,
both commits should be in the released code but they are not. 
[1] https://github.com/apache/beam/pull/7348[2] 
https://github.com/apache/beam/pull/7751
So at least for those 2 features the release notes do not comply to content of 
the release. Is there a real problem or
did I miss something ?
Etienne
Le lundi 04 mars 2019 à 11:42 -0800, Ahmet Altay a écrit :
> Thank you for the additional votes and validations.
> Update: Binaries are pushed. Website updates are blocked on an issue that is 
> preventing beam-site changes to be synced
> the beam website. (INFRA-17953). I am waiting for that to be resolved before 
> sending an announcement.
> On Mon, Mar 4, 2019 at 3:00 AM Robert Bradshaw  wrote:
> > I see the vote has passed, but +1 (binding) from me as well.
> > 
> > 
> > 
> > On Mon, Mar 4, 2019 at 11:51 AM Jean-Baptiste Onofré  
> > wrote:
> > 
> > >
> > 
> > > +1 (binding)
> > 
> > >
> > 
> > > Tested with beam-samples.
> > 
> > >
> > 
> > > Regards
> > 
> > > JB
> > 
> > >
> > 
> > > On 26/02/2019 10:40, Ahmet Altay wrote:
> > 
> > > > Hi everyone,
> > 
> > > >
> > 
> > > > Please review and vote on the release candidate #2 for the version
> > 
> > > > 2.11.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 64B84A5AD91F9C20F5E9D9A7D62E71416096FA00 [3],
> > 
> > > > * all artifacts to be deployed to the Maven Central Repository [4],
> > 
> > > > * source code tag "v2.11.0-RC2" [5],
> > 
> > > > * website pull request listing the release [6] and publishing the API
> > 
> > > > reference manual [7].
> > 
> > > > * Python artifacts are deployed along with the source release to the
> > 
> > > > dist.apache.org  [2].
> > 
> > > > * Validation sheet with a tab for 2.11.0 release to help with validation
> > 
> > > > [8].
> > 
> > > >
> > 
> > > > The vote will be open for at least 72 hours. It is adopted by majority
> > 
> > > > approval, with at least 3 PMC affirmative votes.
> > 
> > > >
> > 
> > > > Thanks,
> > 
> > > > Ahmet
> > 
> > > >
> > 
> > > > [1]
> > 
> > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527&version=12344775
> > 
> > > > [2] https://dist.apache.org/repos/dist/dev/beam/2.11.0/
> > 
> > > > [3] https://dist.apache.org/repos/dist/release/beam/KEYS
> > 
> > > > [4] 
> > > > https://repository.apache.org/content/repositories/orgapachebeam-1064/
> > 
> > > > [5] https://github.com/apache/beam/tree/v2.11.0-RC2
> > 
> > > > [6] https://github.com/apache/beam/pull/7924
> > 
> > > > [7] https://github.com/apache/beam-site/pull/587
> > 
> > > > [8]
> > 
> > > > https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=542393513
> > 
> > > >
> > 
> > >
> > 
> > > --
> > 
> > > Jean-Baptiste Onofré
> > 
> > > jbono...@apache.org
> > 
> > > http://blog.nanthrax.net
> > 
> > > Talend - http://www.talend.com
> > 

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

[Ahmet Altay]

Hi Etienne,

I cut the release branch on 2/14 at [1] (on Feb 14, 2019, 3:52 PM PST --
github timestamp). Release tag, as you pointed out, points to a commit on
Feb 25, 2019 11:48 PM PST. And that is a commit on the release branch.

After cutting the release branch, I only merged cherry picks from master to
the release branch if a JIRA was tagged as a release blocker and there was
a PR to fix that specific issue. In case of these two PRs, they were merged
at Feb 20 and Feb 18 respectively. They were not included in the branch cut
and I did not cherry pick them either. I apologize if I missed a request to
cherry pick these PRs.

Does this answer your question?

Ahmet

[1]
https://github.com/apache/beam/commit/a103edafba569b2fd185b79adffd91aaacb790f0

On Mon, Mar 11, 2019 at 1:50 AM Etienne Chauchot 
wrote:

> @Ahmet sorry I did not have time to check 2.11 release but a fellow Beam
> contributor drew my attention on something:
>
> the 2.11 release tag points on commit of 02/26 and this[1] PR was merged
> 02/20 and that [2] PR was merged on 02/18. So, both commits should be in
> the released code but they are not.
>
> [1] https://github.com/apache/beam/pull/7348
> [2] https://github.com/apache/beam/pull/7751
>
> So at least for those 2 features the release notes do not comply to
> content of the release. Is there a real problem or did I miss something ?
>
> Etienne
>
> Le lundi 04 mars 2019 à 11:42 -0800, Ahmet Altay a écrit :
>
> Thank you for the additional votes and validations.
>
> Update: Binaries are pushed. Website updates are blocked on an issue that
> is preventing beam-site changes to be synced the beam website.
> (INFRA-17953). I am waiting for that to be resolved before sending an
> announcement.
>
> On Mon, Mar 4, 2019 at 3:00 AM Robert Bradshaw 
> wrote:
>
> I see the vote has passed, but +1 (binding) from me as well.
>
> On Mon, Mar 4, 2019 at 11:51 AM Jean-Baptiste Onofré 
> wrote:
> >
> > +1 (binding)
> >
> > Tested with beam-samples.
> >
> > Regards
> > JB
> >
> > On 26/02/2019 10:40, Ahmet Altay wrote:
> > > Hi everyone,
> > >
> > > Please review and vote on the release candidate #2 for the version
> > > 2.11.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 64B84A5AD91F9C20F5E9D9A7D62E71416096FA00 [3],
> > > * all artifacts to be deployed to the Maven Central Repository [4],
> > > * source code tag "v2.11.0-RC2" [5],
> > > * website pull request listing the release [6] and publishing the API
> > > reference manual [7].
> > > * Python artifacts are deployed along with the source release to the
> > > dist.apache.org  [2].
> > > * Validation sheet with a tab for 2.11.0 release to help with
> validation
> > > [8].
> > >
> > > The vote will be open for at least 72 hours. It is adopted by majority
> > > approval, with at least 3 PMC affirmative votes.
> > >
> > > Thanks,
> > > Ahmet
> > >
> > > [1]
> > >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527&version=12344775
> > > [2] https://dist.apache.org/repos/dist/dev/beam/2.11.0/
> > > [3] https://dist.apache.org/repos/dist/release/beam/KEYS
> > > [4]
> https://repository.apache.org/content/repositories/orgapachebeam-1064/
> > > [5] https://github.com/apache/beam/tree/v2.11.0-RC2
> > > [6] https://github.com/apache/beam/pull/7924
> > > [7] https://github.com/apache/beam-site/pull/587
> > > [8]
> > >
> https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=542393513
> > >
> >
> > --
> > Jean-Baptiste Onofré
> > jbono...@apache.org
> > http://blog.nanthrax.net
> > Talend - http://www.talend.com
>
>

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

[Ahmet Altay]

I updated the JIRAs for these two PRs to set the fix version correctly as
2.12.0. That should fix the release notes issue.

On Mon, Mar 11, 2019 at 10:44 AM Ahmet Altay  wrote:

> Hi Etienne,
>
> I cut the release branch on 2/14 at [1] (on Feb 14, 2019, 3:52 PM PST --
> github timestamp). Release tag, as you pointed out, points to a commit on
> Feb 25, 2019 11:48 PM PST. And that is a commit on the release branch.
>
> After cutting the release branch, I only merged cherry picks from master
> to the release branch if a JIRA was tagged as a release blocker and there
> was a PR to fix that specific issue. In case of these two PRs, they were
> merged at Feb 20 and Feb 18 respectively. They were not included in the
> branch cut and I did not cherry pick them either. I apologize if I missed a
> request to cherry pick these PRs.
>
> Does this answer your question?
>
> Ahmet
>
> [1]
> https://github.com/apache/beam/commit/a103edafba569b2fd185b79adffd91aaacb790f0
>
> On Mon, Mar 11, 2019 at 1:50 AM Etienne Chauchot 
> wrote:
>
>> @Ahmet sorry I did not have time to check 2.11 release but a fellow Beam
>> contributor drew my attention on something:
>>
>> the 2.11 release tag points on commit of 02/26 and this[1] PR was merged
>> 02/20 and that [2] PR was merged on 02/18. So, both commits should be in
>> the released code but they are not.
>>
>> [1] https://github.com/apache/beam/pull/7348
>> [2] https://github.com/apache/beam/pull/7751
>>
>> So at least for those 2 features the release notes do not comply to
>> content of the release. Is there a real problem or did I miss something ?
>>
>> Etienne
>>
>> Le lundi 04 mars 2019 à 11:42 -0800, Ahmet Altay a écrit :
>>
>> Thank you for the additional votes and validations.
>>
>> Update: Binaries are pushed. Website updates are blocked on an issue that
>> is preventing beam-site changes to be synced the beam website.
>> (INFRA-17953). I am waiting for that to be resolved before sending an
>> announcement.
>>
>> On Mon, Mar 4, 2019 at 3:00 AM Robert Bradshaw 
>> wrote:
>>
>> I see the vote has passed, but +1 (binding) from me as well.
>>
>> On Mon, Mar 4, 2019 at 11:51 AM Jean-Baptiste Onofré 
>> wrote:
>> >
>> > +1 (binding)
>> >
>> > Tested with beam-samples.
>> >
>> > Regards
>> > JB
>> >
>> > On 26/02/2019 10:40, Ahmet Altay wrote:
>> > > Hi everyone,
>> > >
>> > > Please review and vote on the release candidate #2 for the version
>> > > 2.11.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 64B84A5AD91F9C20F5E9D9A7D62E71416096FA00 [3],
>> > > * all artifacts to be deployed to the Maven Central Repository [4],
>> > > * source code tag "v2.11.0-RC2" [5],
>> > > * website pull request listing the release [6] and publishing the API
>> > > reference manual [7].
>> > > * Python artifacts are deployed along with the source release to the
>> > > dist.apache.org  [2].
>> > > * Validation sheet with a tab for 2.11.0 release to help with
>> validation
>> > > [8].
>> > >
>> > > The vote will be open for at least 72 hours. It is adopted by majority
>> > > approval, with at least 3 PMC affirmative votes.
>> > >
>> > > Thanks,
>> > > Ahmet
>> > >
>> > > [1]
>> > >
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527&version=12344775
>> > > [2] https://dist.apache.org/repos/dist/dev/beam/2.11.0/
>> > > [3] https://dist.apache.org/repos/dist/release/beam/KEYS
>> > > [4]
>> https://repository.apache.org/content/repositories/orgapachebeam-1064/
>> > > [5] https://github.com/apache/beam/tree/v2.11.0-RC2
>> > > [6] https://github.com/apache/beam/pull/7924
>> > > [7] https://github.com/apache/beam-site/pull/587
>> > > [8]
>> > >
>> https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=542393513
>> > >
>> >
>> > --
>> > Jean-Baptiste Onofré
>> > jbono...@apache.org
>> > http://blog.nanthrax.net
>> > Talend - http://www.talend.com
>>
>>

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

[Thomas Weise]

Ahmet, thanks managing the release!

I have a suggestion (not specific to only this release):

The release blogs could be more useful to users. In this case, we have a
long list of dependency updates on the top, but probably the improvements
and features section should come first. I was also very surprised to find
"Portable Flink runner support for running cross-language transforms."
mentioned, since that is only being worked on now. On the other hand, there
are probably items that we miss.

Since this can only be addressed by more eyes, I suggest that going forward
the blog pull request is included and reviewed as part of the release vote.

Also, we should make announcing the release on Twitter part of the process.

Thanks,
Thomas


On Mon, Mar 11, 2019 at 10:46 AM Ahmet Altay  wrote:

> I updated the JIRAs for these two PRs to set the fix version correctly as
> 2.12.0. That should fix the release notes issue.
>
> On Mon, Mar 11, 2019 at 10:44 AM Ahmet Altay  wrote:
>
>> Hi Etienne,
>>
>> I cut the release branch on 2/14 at [1] (on Feb 14, 2019, 3:52 PM PST --
>> github timestamp). Release tag, as you pointed out, points to a commit on
>> Feb 25, 2019 11:48 PM PST. And that is a commit on the release branch.
>>
>> After cutting the release branch, I only merged cherry picks from master
>> to the release branch if a JIRA was tagged as a release blocker and there
>> was a PR to fix that specific issue. In case of these two PRs, they were
>> merged at Feb 20 and Feb 18 respectively. They were not included in the
>> branch cut and I did not cherry pick them either. I apologize if I missed a
>> request to cherry pick these PRs.
>>
>> Does this answer your question?
>>
>> Ahmet
>>
>> [1]
>> https://github.com/apache/beam/commit/a103edafba569b2fd185b79adffd91aaacb790f0
>>
>> On Mon, Mar 11, 2019 at 1:50 AM Etienne Chauchot 
>> wrote:
>>
>>> @Ahmet sorry I did not have time to check 2.11 release but a fellow Beam
>>> contributor drew my attention on something:
>>>
>>> the 2.11 release tag points on commit of 02/26 and this[1] PR was merged
>>> 02/20 and that [2] PR was merged on 02/18. So, both commits should be in
>>> the released code but they are not.
>>>
>>> [1] https://github.com/apache/beam/pull/7348
>>> [2] https://github.com/apache/beam/pull/7751
>>>
>>> So at least for those 2 features the release notes do not comply to
>>> content of the release. Is there a real problem or did I miss something ?
>>>
>>> Etienne
>>>
>>> Le lundi 04 mars 2019 à 11:42 -0800, Ahmet Altay a écrit :
>>>
>>> Thank you for the additional votes and validations.
>>>
>>> Update: Binaries are pushed. Website updates are blocked on an issue
>>> that is preventing beam-site changes to be synced the beam website.
>>> (INFRA-17953). I am waiting for that to be resolved before sending an
>>> announcement.
>>>
>>> On Mon, Mar 4, 2019 at 3:00 AM Robert Bradshaw 
>>> wrote:
>>>
>>> I see the vote has passed, but +1 (binding) from me as well.
>>>
>>> On Mon, Mar 4, 2019 at 11:51 AM Jean-Baptiste Onofré 
>>> wrote:
>>> >
>>> > +1 (binding)
>>> >
>>> > Tested with beam-samples.
>>> >
>>> > Regards
>>> > JB
>>> >
>>> > On 26/02/2019 10:40, Ahmet Altay wrote:
>>> > > Hi everyone,
>>> > >
>>> > > Please review and vote on the release candidate #2 for the version
>>> > > 2.11.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 64B84A5AD91F9C20F5E9D9A7D62E71416096FA00 [3],
>>> > > * all artifacts to be deployed to the Maven Central Repository [4],
>>> > > * source code tag "v2.11.0-RC2" [5],
>>> > > * website pull request listing the release [6] and publishing the API
>>> > > reference manual [7].
>>> > > * Python artifacts are deployed along with the source release to the
>>> > > dist.apache.org  [2].
>>> > > * Validation sheet with a tab for 2.11.0 release to help with
>>> validation
>>> > > [8].
>>> > >
>>> > > The vote will be open for at least 72 hours. It is adopted by
>>> majority
>>> > > approval, with at least 3 PMC affirmative votes.
>>> > >
>>> > > Thanks,
>>> > > Ahmet
>>> > >
>>> > > [1]
>>> > >
>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527&version=12344775
>>> > > [2] https://dist.apache.org/repos/dist/dev/beam/2.11.0/
>>> > > [3] https://dist.apache.org/repos/dist/release/beam/KEYS
>>> > > [4]
>>> https://repository.apache.org/content/repositories/orgapachebeam-1064/
>>> > > [5] https://github.com/apache/beam/tree/v2.11.0-RC2
>>> > > [6] https://github.com/apache/beam/pull/7924
>>> > > [7] https://github.com/apache/beam-site/pull/587
>>> > > [8]
>>> > >
>>> https://docs.google.com/spreadsheets/d/1qk

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

[Kenneth Knowles]

That is a good idea. The blog post is probably the main avenue where folks
will find out about new features or big fixes.

When I did 2.10.0 I just used the automated Jira release notes and pulled
out significant things based on my judgment. I would also suggest that our
Jira hygiene could be significantly improved to make this process more
effective.

Kenn

On Mon, Mar 11, 2019 at 1:04 PM Thomas Weise  wrote:

> Ahmet, thanks managing the release!
>
> I have a suggestion (not specific to only this release):
>
> The release blogs could be more useful to users. In this case, we have a
> long list of dependency updates on the top, but probably the improvements
> and features section should come first. I was also very surprised to find
> "Portable Flink runner support for running cross-language transforms."
> mentioned, since that is only being worked on now. On the other hand, there
> are probably items that we miss.
>
> Since this can only be addressed by more eyes, I suggest that going
> forward the blog pull request is included and reviewed as part of the
> release vote.
>
> Also, we should make announcing the release on Twitter part of the process.
>
> Thanks,
> Thomas
>
>
> On Mon, Mar 11, 2019 at 10:46 AM Ahmet Altay  wrote:
>
>> I updated the JIRAs for these two PRs to set the fix version correctly as
>> 2.12.0. That should fix the release notes issue.
>>
>> On Mon, Mar 11, 2019 at 10:44 AM Ahmet Altay  wrote:
>>
>>> Hi Etienne,
>>>
>>> I cut the release branch on 2/14 at [1] (on Feb 14, 2019, 3:52 PM PST --
>>> github timestamp). Release tag, as you pointed out, points to a commit on
>>> Feb 25, 2019 11:48 PM PST. And that is a commit on the release branch.
>>>
>>> After cutting the release branch, I only merged cherry picks from master
>>> to the release branch if a JIRA was tagged as a release blocker and there
>>> was a PR to fix that specific issue. In case of these two PRs, they were
>>> merged at Feb 20 and Feb 18 respectively. They were not included in the
>>> branch cut and I did not cherry pick them either. I apologize if I missed a
>>> request to cherry pick these PRs.
>>>
>>> Does this answer your question?
>>>
>>> Ahmet
>>>
>>> [1]
>>> https://github.com/apache/beam/commit/a103edafba569b2fd185b79adffd91aaacb790f0
>>>
>>> On Mon, Mar 11, 2019 at 1:50 AM Etienne Chauchot 
>>> wrote:
>>>
 @Ahmet sorry I did not have time to check 2.11 release but a fellow
 Beam contributor drew my attention on something:

 the 2.11 release tag points on commit of 02/26 and this[1] PR was
 merged 02/20 and that [2] PR was merged on 02/18. So, both commits should
 be in the released code but they are not.

 [1] https://github.com/apache/beam/pull/7348
 [2] https://github.com/apache/beam/pull/7751

 So at least for those 2 features the release notes do not comply to
 content of the release. Is there a real problem or did I miss something ?

 Etienne

 Le lundi 04 mars 2019 à 11:42 -0800, Ahmet Altay a écrit :

 Thank you for the additional votes and validations.

 Update: Binaries are pushed. Website updates are blocked on an issue
 that is preventing beam-site changes to be synced the beam website.
 (INFRA-17953). I am waiting for that to be resolved before sending an
 announcement.

 On Mon, Mar 4, 2019 at 3:00 AM Robert Bradshaw 
 wrote:

 I see the vote has passed, but +1 (binding) from me as well.

 On Mon, Mar 4, 2019 at 11:51 AM Jean-Baptiste Onofré 
 wrote:
 >
 > +1 (binding)
 >
 > Tested with beam-samples.
 >
 > Regards
 > JB
 >
 > On 26/02/2019 10:40, Ahmet Altay wrote:
 > > Hi everyone,
 > >
 > > Please review and vote on the release candidate #2 for the version
 > > 2.11.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 64B84A5AD91F9C20F5E9D9A7D62E71416096FA00 [3],
 > > * all artifacts to be deployed to the Maven Central Repository [4],
 > > * source code tag "v2.11.0-RC2" [5],
 > > * website pull request listing the release [6] and publishing the
 API
 > > reference manual [7].
 > > * Python artifacts are deployed along with the source release to the
 > > dist.apache.org  [2].
 > > * Validation sheet with a tab for 2.11.0 release to help with
 validation
 > > [8].
 > >
 > > The vote will be open for at least 72 hours. It is adopted by
 majority
 > > approval, with at least 3 PMC affirmative votes.
 > >
 > > Thanks,
 > > Ahmet
 > >

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

[Ahmet Altay]

I agree this is a good idea. I used the same technique for 2.11 blog post
(JIRA release notes -> editorialized list + diffed the dependencies).

On Mon, Mar 11, 2019 at 1:40 PM Kenneth Knowles  wrote:

> That is a good idea. The blog post is probably the main avenue where folks
> will find out about new features or big fixes.
>
> When I did 2.10.0 I just used the automated Jira release notes and pulled
> out significant things based on my judgment. I would also suggest that our
> Jira hygiene could be significantly improved to make this process more
> effective.
>

+1 to improving JIRA notes as well. Often times issues are closed with no
real comments on what happened, has it been resolved or not. It becomes an
exercise on reading the linked PRs to figure out what happened.


>
> Kenn
>
> On Mon, Mar 11, 2019 at 1:04 PM Thomas Weise  wrote:
>
>> Ahmet, thanks managing the release!
>>
>> I have a suggestion (not specific to only this release):
>>
>> The release blogs could be more useful to users. In this case, we have a
>> long list of dependency updates on the top, but probably the improvements
>> and features section should come first. I was also very surprised to find
>> "Portable Flink runner support for running cross-language transforms."
>> mentioned, since that is only being worked on now. On the other hand, there
>> are probably items that we miss.
>>
>> Since this can only be addressed by more eyes, I suggest that going
>> forward the blog pull request is included and reviewed as part of the
>> release vote.
>>
>> Also, we should make announcing the release on Twitter part of the
>> process.
>>
>
This is actually part of the release process (
https://beam.apache.org/contribute/release-guide/#social-media). I missed
it for 2.11. I will send an announcement on Twitter shortly.


>
>> Thanks,
>> Thomas
>>
>>
>> On Mon, Mar 11, 2019 at 10:46 AM Ahmet Altay  wrote:
>>
>>> I updated the JIRAs for these two PRs to set the fix version correctly
>>> as 2.12.0. That should fix the release notes issue.
>>>
>>> On Mon, Mar 11, 2019 at 10:44 AM Ahmet Altay  wrote:
>>>
 Hi Etienne,

 I cut the release branch on 2/14 at [1] (on Feb 14, 2019, 3:52 PM PST
 -- github timestamp). Release tag, as you pointed out, points to a commit
 on Feb 25, 2019 11:48 PM PST. And that is a commit on the release branch.

 After cutting the release branch, I only merged cherry picks from
 master to the release branch if a JIRA was tagged as a release blocker and
 there was a PR to fix that specific issue. In case of these two PRs, they
 were merged at Feb 20 and Feb 18 respectively. They were not included in
 the branch cut and I did not cherry pick them either. I apologize if I
 missed a request to cherry pick these PRs.

 Does this answer your question?

 Ahmet

 [1]
 https://github.com/apache/beam/commit/a103edafba569b2fd185b79adffd91aaacb790f0

 On Mon, Mar 11, 2019 at 1:50 AM Etienne Chauchot 
 wrote:

> @Ahmet sorry I did not have time to check 2.11 release but a fellow
> Beam contributor drew my attention on something:
>
> the 2.11 release tag points on commit of 02/26 and this[1] PR was
> merged 02/20 and that [2] PR was merged on 02/18. So, both commits should
> be in the released code but they are not.
>
> [1] https://github.com/apache/beam/pull/7348
> [2] https://github.com/apache/beam/pull/7751
>
> So at least for those 2 features the release notes do not comply to
> content of the release. Is there a real problem or did I miss something ?
>
> Etienne
>
> Le lundi 04 mars 2019 à 11:42 -0800, Ahmet Altay a écrit :
>
> Thank you for the additional votes and validations.
>
> Update: Binaries are pushed. Website updates are blocked on an issue
> that is preventing beam-site changes to be synced the beam website.
> (INFRA-17953). I am waiting for that to be resolved before sending an
> announcement.
>
> On Mon, Mar 4, 2019 at 3:00 AM Robert Bradshaw 
> wrote:
>
> I see the vote has passed, but +1 (binding) from me as well.
>
> On Mon, Mar 4, 2019 at 11:51 AM Jean-Baptiste Onofré 
> wrote:
> >
> > +1 (binding)
> >
> > Tested with beam-samples.
> >
> > Regards
> > JB
> >
> > On 26/02/2019 10:40, Ahmet Altay wrote:
> > > Hi everyone,
> > >
> > > Please review and vote on the release candidate #2 for the version
> > > 2.11.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.11.0, release candidate #2

[Etienne Chauchot]

Ahmet, Yes  in a comment in this ticket 
https://issues.apache.org/jira/browse/BEAM-6292  I supposed there were cherry
picks.Thanks for the confirmation !
No problem about not having cherry picked these PRs they were not release 
blockers. It is just that these features were
announced for 2.11 in the release notes. My bad, I did not know the release cut 
date of 02/14 I should have targeted
them to 2.12 then.
Thanks
Etienne
Le lundi 11 mars 2019 à 10:44 -0700, Ahmet Altay a écrit :
> Hi Etienne,
> 
> I cut the release branch on 2/14 at [1] (on Feb 14, 2019, 3:52 PM PST -- 
> github timestamp). Release tag, as you
> pointed out, points to a commit on Feb 25, 2019 11:48 PM PST. And that is a 
> commit on the release branch. 
> 
> After cutting the release branch, I only merged cherry picks from master to 
> the release branch if a JIRA was tagged as
> a release blocker and there was a PR to fix that specific issue. In case of 
> these two PRs, they were merged at Feb 20
> and Feb 18 respectively. They were not included in the branch cut and I did 
> not cherry pick them either. I apologize
> if I missed a request to cherry pick these PRs.
> 
> Does this answer your question?
> 
> Ahmet
> 
> [1] 
> https://github.com/apache/beam/commit/a103edafba569b2fd185b79adffd91aaacb790f0
> On Mon, Mar 11, 2019 at 1:50 AM Etienne Chauchot  wrote:
> > @Ahmet sorry I did not have time to check 2.11 release but a fellow Beam 
> > contributor drew my attention on something:
> > the 2.11 release tag points on commit of 02/26 and this[1] PR was merged 
> > 02/20 and that [2] PR was merged on 02/18.
> > So, both commits should be in the released code but they are not. 
> > [1] https://github.com/apache/beam/pull/7348[2] 
> > https://github.com/apache/beam/pull/7751
> > So at least for those 2 features the release notes do not comply to content 
> > of the release. Is there a real problem
> > or did I miss something ?
> > Etienne
> > Le lundi 04 mars 2019 à 11:42 -0800, Ahmet Altay a écrit :
> > > Thank you for the additional votes and validations.
> > > Update: Binaries are pushed. Website updates are blocked on an issue that 
> > > is preventing beam-site changes to be
> > > synced the beam website. (INFRA-17953). I am waiting for that to be 
> > > resolved before sending an announcement.
> > > On Mon, Mar 4, 2019 at 3:00 AM Robert Bradshaw  
> > > wrote:
> > > > I see the vote has passed, but +1 (binding) from me as well.
> > > > 
> > > > 
> > > > 
> > > > On Mon, Mar 4, 2019 at 11:51 AM Jean-Baptiste Onofré 
> > > >  wrote:
> > > > 
> > > > >
> > > > 
> > > > > +1 (binding)
> > > > 
> > > > >
> > > > 
> > > > > Tested with beam-samples.
> > > > 
> > > > >
> > > > 
> > > > > Regards
> > > > 
> > > > > JB
> > > > 
> > > > >
> > > > 
> > > > > On 26/02/2019 10:40, Ahmet Altay wrote:
> > > > 
> > > > > > Hi everyone,
> > > > 
> > > > > >
> > > > 
> > > > > > Please review and vote on the release candidate #2 for the version
> > > > 
> > > > > > 2.11.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 64B84A5AD91F9C20F5E9D9A7D62E71416096FA00 [3],
> > > > 
> > > > > > * all artifacts to be deployed to the Maven Central Repository [4],
> > > > 
> > > > > > * source code tag "v2.11.0-RC2" [5],
> > > > 
> > > > > > * website pull request listing the release [6] and publishing the 
> > > > > > API
> > > > 
> > > > > > reference manual [7].
> > > > 
> > > > > > * Python artifacts are deployed along with the source release to the
> > > > 
> > > > > > dist.apache.org  [2].
> > > > 
> > > > > > * Validation sheet with a tab for 2.11.0 release to help with 
> > > > > > validation
> > > > 
> > > > > > [8].
> > > > 
> > > > > >
> > > > 
> > > > > > The vote will be open for at least 72 hours. It is adopted by 
> > > > > > majority
> > > > 
> > > > > > approval, with at least 3 PMC affirmative votes.
> > > > 
> > > > > >
> > > > 
> > > > > > Thanks,
> > > > 
> > > > > > Ahmet
> > > > 
> > > > > >
> > > > 
> > > > > > [1]
> > > > 
> > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527&version=12344775
> > > > 
> > > > > > [2] https://dist.apache.org/repos/dist/dev/beam/2.11.0/
> > > > 
> > > > > > [3] https://dist.apache.org/repos/dist/release/beam/KEYS
> > > > 
> > > > > > [4] 
> > > > > > https://repository.apache.org/content/repositories/orgapachebeam-1064/
> > > > 
> > > > > > [5] https://github.com/apache/beam/tree/v2.11.0-RC2
> > > > 
> > > > > > [6] https://gi