[RESULT] [VOTE] Release 2.14.0, release candidate #1

[Anton Kedin]

I'm happy to announce that we have unanimously approved this release.

There are 7 approving votes, 4 of which are binding (in order):
* Ahmet (al...@google.com);
* Robert (rober...@google.com);
* Pablo (pabl...@google.com);
* Ismaël (ieme...@gmail.com);

There are no disapproving votes.

Thanks everyone!

Next step is to finalize the release (merge the docs/website/blog PRs,
publish artifacts), I will be working on it tomorrow (PST, Seattle time).

Please let me know if you have any questions, concerns or if I made a
mistake somewhere.

Regards,
Anton

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

[Chamikara Jayalath]

+1 for continuing with RC1 with a notice about this issue. I marked this as
a blocker for 2.15.0.

Thanks,
Cham

On Wed, Jul 31, 2019 at 3:28 PM Anton Kedin  wrote:

> I am planning to close the vote tonight and this is the only potential
> blocker discovered so far. So I strongly prefer to finalize the
> current candidate to not delay the release further, since, as Ahmet
> mentioned, this is a new functionality and not a regression, and is
> experimental. However, given the severity of the issue, cutting another
> candidate is definitely an option and if we can go this path as well.
>
> Regards,
> Anton
>
> On Wed, Jul 31, 2019 at 3:16 PM Eugene Kirpichov 
> wrote:
>
>> I would recommend that the known issue notice about this source at least
>> be strongly worded - this source in the current state should be marked "DO
>> NOT USE" - it will produce data loss in *most* production use cases.
>> That still leaves the risk that people will use it anyway; up to folks
>> driving the release to decide whether it's worth cutting a new candidate
>> for the sake of just temporarily removing this source, or a notice in
>> release notes is sufficient.
>>
>> On Wed, Jul 31, 2019 at 2:59 PM Ahmet Altay  wrote:
>>
>>> Since the python mongodb source is new in this release (not a
>>> regression) and experimental, I agree with adding a known issues notice to
>>> the release notes instead of starting a RC2 only for this issue.
>>>
>>> On Wed, Jul 31, 2019 at 2:47 PM Chamikara Jayalath 
>>> wrote:
>>>
 FYI we found a critical issue with the Python MongoDB source that is
 included with this release:
 https://issues.apache.org/jira/browse/BEAM-7866
 I suggest we include a clear notice in the release about this issue if
 the release vote has already been finalized or make this a blocker if we
 are going for a RC2.

 Thanks,
 Cham

 On Wed, Jul 31, 2019 at 2:31 AM Robert Bradshaw 
 wrote:

> On Wed, Jul 31, 2019 at 11:22 AM Valentyn Tymofieiev <
> valen...@google.com> wrote:
>
>> I have checked Portable Wordcount example on Flink and Spark on
>> Python 2 and Python 3.
>>
>> To do so, I had to checkout Beam from git repo, since using the
>> source distribution does not include gradlew, and gradelw_orig did not 
>> work
>> for me. Commands I ran:
>>
>> git checkout tags/v2.14.0-RC1
>> ./gradlew :sdks:python:container:py3:docker
>> ./gradlew :runners:flink:1.5:job-server:runShadow# Use  ./gradlew
>> :runners:spark:job-server:runShadow for Spark
>> ./gradlew
>> :sdks:python:test-suites:portable:py35:portableWordCountBatch
>>  -PjobEndpoint=localhost:8099 -PenvironmentType=LOOPBACK
>> cat /tmp/py-wordcount-direct* # to verify results.
>>
>> Loopback scenarios worked, however DOCKER scenarios did not. Opened
>> several Jiras to follow up:
>>
>> https://issues.apache.org/jira/browse/BEAM-7857
>> https://issues.apache.org/jira/browse/BEAM-7858
>> https://issues.apache.org/jira/browse/BEAM-7859
>> 
>>
>
> I commented on the bugs, and I think this is due to trying to use
> Docker mode with local files (a known issue).
>
>
>> The gradle targets that were required to run these tests are not
>> present in 2.13.0 branch, so I don't consider it a regression and still
>> cast +1.
>>
>
> Agreed.
>
>
>> On Wed, Jul 31, 2019 at 11:31 AM Ismaël Mejía 
>> wrote:
>>
>>> Oups Robert pointed to me that I have probably not counted correctly.
>>> There were indeed already 3 PMC +1 votes. Pablo, Robert and Ahmet.
>>> Please excuse me for the extra noise.
>>>
>>> On Wed, Jul 31, 2019 at 9:46 AM Ismaël Mejía 
>>> wrote:
>>> >
>>> > To complete the release we need to have at least three +1 binding
>>> > votes (votes from PMC members) as stated in [1]. So far we have
>>> only
>>> > 2.
>>> >
>>> > Thomas (and the others). The blog post PR is now open [2] please
>>> help
>>> > us add missing features or maybe to highlight the ones you consider
>>> > important in the PR comments.
>>> >
>>> > Here it is the missing +1 (binding). Validated SHAs+signatures,
>>> > beam-samples and one internal company project with the new jars.
>>> > Compared source file vs tagged git repo. Everything looks ok.
>>> >
>>> > [1] https://www.apache.org/foundation/voting.html#ReleaseVotes
>>> > [2] https://github.com/apache/beam/pull/9201/files
>>> >
>>> > On Wed, Jul 31, 2019 at 6:27 AM Anton Kedin 
>>> wrote:
>>> > >
>>> > > Ran various postcommits, validates runners, and nexmark against
>>> the release branch. All looks good so far.
>>> > >
>>> > > Will take another look at the docs/blog and the nexmark numbers
>>> tomorrow, but if nothing comes up I will close the vote 

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

[Eugene Kirpichov]

I would recommend that the known issue notice about this source at least be
strongly worded - this source in the current state should be marked "DO NOT
USE" - it will produce data loss in *most* production use cases. That still
leaves the risk that people will use it anyway; up to folks driving the
release to decide whether it's worth cutting a new candidate for the sake
of just temporarily removing this source, or a notice in release notes is
sufficient.

On Wed, Jul 31, 2019 at 2:59 PM Ahmet Altay  wrote:

> Since the python mongodb source is new in this release (not a regression)
> and experimental, I agree with adding a known issues notice to the release
> notes instead of starting a RC2 only for this issue.
>
> On Wed, Jul 31, 2019 at 2:47 PM Chamikara Jayalath 
> wrote:
>
>> FYI we found a critical issue with the Python MongoDB source that is
>> included with this release:
>> https://issues.apache.org/jira/browse/BEAM-7866
>> I suggest we include a clear notice in the release about this issue if
>> the release vote has already been finalized or make this a blocker if we
>> are going for a RC2.
>>
>> Thanks,
>> Cham
>>
>> On Wed, Jul 31, 2019 at 2:31 AM Robert Bradshaw 
>> wrote:
>>
>>> On Wed, Jul 31, 2019 at 11:22 AM Valentyn Tymofieiev <
>>> valen...@google.com> wrote:
>>>
 I have checked Portable Wordcount example on Flink and Spark on Python
 2 and Python 3.

 To do so, I had to checkout Beam from git repo, since using the source
 distribution does not include gradlew, and gradelw_orig did not work for
 me. Commands I ran:

 git checkout tags/v2.14.0-RC1
 ./gradlew :sdks:python:container:py3:docker
 ./gradlew :runners:flink:1.5:job-server:runShadow# Use  ./gradlew
 :runners:spark:job-server:runShadow for Spark
 ./gradlew :sdks:python:test-suites:portable:py35:portableWordCountBatch
  -PjobEndpoint=localhost:8099 -PenvironmentType=LOOPBACK
 cat /tmp/py-wordcount-direct* # to verify results.

 Loopback scenarios worked, however DOCKER scenarios did not. Opened
 several Jiras to follow up:

 https://issues.apache.org/jira/browse/BEAM-7857
 https://issues.apache.org/jira/browse/BEAM-7858
 https://issues.apache.org/jira/browse/BEAM-7859
 

>>>
>>> I commented on the bugs, and I think this is due to trying to use Docker
>>> mode with local files (a known issue).
>>>
>>>
 The gradle targets that were required to run these tests are not
 present in 2.13.0 branch, so I don't consider it a regression and still
 cast +1.

>>>
>>> Agreed.
>>>
>>>
 On Wed, Jul 31, 2019 at 11:31 AM Ismaël Mejía 
 wrote:

> Oups Robert pointed to me that I have probably not counted correctly.
> There were indeed already 3 PMC +1 votes. Pablo, Robert and Ahmet.
> Please excuse me for the extra noise.
>
> On Wed, Jul 31, 2019 at 9:46 AM Ismaël Mejía 
> wrote:
> >
> > To complete the release we need to have at least three +1 binding
> > votes (votes from PMC members) as stated in [1]. So far we have only
> > 2.
> >
> > Thomas (and the others). The blog post PR is now open [2] please help
> > us add missing features or maybe to highlight the ones you consider
> > important in the PR comments.
> >
> > Here it is the missing +1 (binding). Validated SHAs+signatures,
> > beam-samples and one internal company project with the new jars.
> > Compared source file vs tagged git repo. Everything looks ok.
> >
> > [1] https://www.apache.org/foundation/voting.html#ReleaseVotes
> > [2] https://github.com/apache/beam/pull/9201/files
> >
> > On Wed, Jul 31, 2019 at 6:27 AM Anton Kedin 
> wrote:
> > >
> > > Ran various postcommits, validates runners, and nexmark against
> the release branch. All looks good so far.
> > >
> > > Will take another look at the docs/blog and the nexmark numbers
> tomorrow, but if nothing comes up I will close the vote tomorrow
> (Wednesday) by 6pm PST (= Thursday 01:00am UTC) since it's over 72hours
> since the vote has started and we have a number of +1s including PMC
> members and no -1s.
> > >
> > > Regards,
> > > Anton
> > >
> > > On Tue, Jul 30, 2019 at 8:13 PM Valentyn Tymofieiev <
> valen...@google.com> wrote:
> > >>
> > >> I also ran unit tests for Python 3.7 and they passed as well.
> Cython tests for python3.7 require  `apt-get install python3.7-dev`.
> > >>
> > >> On Wed, Jul 31, 2019 at 3:16 AM Pablo Estrada 
> wrote:
> > >>>
> > >>> +1
> > >>>
> > >>> I installed from source, and ran unit tests for Python in 2.7,
> 3.5, 3.6.
> > >>>
> > >>> Also ran a number of integration tests on Py 3.5 on Dataflow and
> DirectRunner.
> > >>> Best
> > >>> -P.
> > >>>
> > >>> On Tue, Jul 30, 2019 at 11:09 AM Hannah 

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

[Ahmet Altay]

Since the python mongodb source is new in this release (not a regression)
and experimental, I agree with adding a known issues notice to the release
notes instead of starting a RC2 only for this issue.

On Wed, Jul 31, 2019 at 2:47 PM Chamikara Jayalath 
wrote:

> FYI we found a critical issue with the Python MongoDB source that is
> included with this release:
> https://issues.apache.org/jira/browse/BEAM-7866
> I suggest we include a clear notice in the release about this issue if the
> release vote has already been finalized or make this a blocker if we are
> going for a RC2.
>
> Thanks,
> Cham
>
> On Wed, Jul 31, 2019 at 2:31 AM Robert Bradshaw 
> wrote:
>
>> On Wed, Jul 31, 2019 at 11:22 AM Valentyn Tymofieiev 
>> wrote:
>>
>>> I have checked Portable Wordcount example on Flink and Spark on Python 2
>>> and Python 3.
>>>
>>> To do so, I had to checkout Beam from git repo, since using the source
>>> distribution does not include gradlew, and gradelw_orig did not work for
>>> me. Commands I ran:
>>>
>>> git checkout tags/v2.14.0-RC1
>>> ./gradlew :sdks:python:container:py3:docker
>>> ./gradlew :runners:flink:1.5:job-server:runShadow# Use  ./gradlew
>>> :runners:spark:job-server:runShadow for Spark
>>> ./gradlew :sdks:python:test-suites:portable:py35:portableWordCountBatch
>>>  -PjobEndpoint=localhost:8099 -PenvironmentType=LOOPBACK
>>> cat /tmp/py-wordcount-direct* # to verify results.
>>>
>>> Loopback scenarios worked, however DOCKER scenarios did not. Opened
>>> several Jiras to follow up:
>>>
>>> https://issues.apache.org/jira/browse/BEAM-7857
>>> https://issues.apache.org/jira/browse/BEAM-7858
>>> https://issues.apache.org/jira/browse/BEAM-7859
>>> 
>>>
>>
>> I commented on the bugs, and I think this is due to trying to use Docker
>> mode with local files (a known issue).
>>
>>
>>> The gradle targets that were required to run these tests are not present
>>> in 2.13.0 branch, so I don't consider it a regression and still cast +1.
>>>
>>
>> Agreed.
>>
>>
>>> On Wed, Jul 31, 2019 at 11:31 AM Ismaël Mejía  wrote:
>>>
 Oups Robert pointed to me that I have probably not counted correctly.
 There were indeed already 3 PMC +1 votes. Pablo, Robert and Ahmet.
 Please excuse me for the extra noise.

 On Wed, Jul 31, 2019 at 9:46 AM Ismaël Mejía  wrote:
 >
 > To complete the release we need to have at least three +1 binding
 > votes (votes from PMC members) as stated in [1]. So far we have only
 > 2.
 >
 > Thomas (and the others). The blog post PR is now open [2] please help
 > us add missing features or maybe to highlight the ones you consider
 > important in the PR comments.
 >
 > Here it is the missing +1 (binding). Validated SHAs+signatures,
 > beam-samples and one internal company project with the new jars.
 > Compared source file vs tagged git repo. Everything looks ok.
 >
 > [1] https://www.apache.org/foundation/voting.html#ReleaseVotes
 > [2] https://github.com/apache/beam/pull/9201/files
 >
 > On Wed, Jul 31, 2019 at 6:27 AM Anton Kedin  wrote:
 > >
 > > Ran various postcommits, validates runners, and nexmark against the
 release branch. All looks good so far.
 > >
 > > Will take another look at the docs/blog and the nexmark numbers
 tomorrow, but if nothing comes up I will close the vote tomorrow
 (Wednesday) by 6pm PST (= Thursday 01:00am UTC) since it's over 72hours
 since the vote has started and we have a number of +1s including PMC
 members and no -1s.
 > >
 > > Regards,
 > > Anton
 > >
 > > On Tue, Jul 30, 2019 at 8:13 PM Valentyn Tymofieiev <
 valen...@google.com> wrote:
 > >>
 > >> I also ran unit tests for Python 3.7 and they passed as well.
 Cython tests for python3.7 require  `apt-get install python3.7-dev`.
 > >>
 > >> On Wed, Jul 31, 2019 at 3:16 AM Pablo Estrada 
 wrote:
 > >>>
 > >>> +1
 > >>>
 > >>> I installed from source, and ran unit tests for Python in 2.7,
 3.5, 3.6.
 > >>>
 > >>> Also ran a number of integration tests on Py 3.5 on Dataflow and
 DirectRunner.
 > >>> Best
 > >>> -P.
 > >>>
 > >>> On Tue, Jul 30, 2019 at 11:09 AM Hannah Jiang <
 hannahji...@google.com> wrote:
 > 
 >  I checked Py3 tests using .zip, mainly with direct runners, and
 everything looks good, so +1.
 > 
 >  On Tue, Jul 30, 2019 at 2:08 AM Robert Bradshaw <
 rober...@google.com> wrote:
 > >
 > > I checked all the artifact signatures and ran a couple test
 pipelines with the wheels (Py2 and Py3) and everything looked good to me,
 so +1.
 > >
 > > On Mon, Jul 29, 2019 at 8:29 PM Valentyn Tymofieiev <
 valen...@google.com> wrote:
 > >>
 > >> I have checked Python 3 batch and streaming quickstarts on
 Dataflow runner using 

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

[Chamikara Jayalath]

FYI we found a critical issue with the Python MongoDB source that is
included with this release: https://issues.apache.org/jira/browse/BEAM-7866
I suggest we include a clear notice in the release about this issue if the
release vote has already been finalized or make this a blocker if we are
going for a RC2.

Thanks,
Cham

On Wed, Jul 31, 2019 at 2:31 AM Robert Bradshaw  wrote:

> On Wed, Jul 31, 2019 at 11:22 AM Valentyn Tymofieiev 
> wrote:
>
>> I have checked Portable Wordcount example on Flink and Spark on Python 2
>> and Python 3.
>>
>> To do so, I had to checkout Beam from git repo, since using the source
>> distribution does not include gradlew, and gradelw_orig did not work for
>> me. Commands I ran:
>>
>> git checkout tags/v2.14.0-RC1
>> ./gradlew :sdks:python:container:py3:docker
>> ./gradlew :runners:flink:1.5:job-server:runShadow# Use  ./gradlew
>> :runners:spark:job-server:runShadow for Spark
>> ./gradlew :sdks:python:test-suites:portable:py35:portableWordCountBatch
>>  -PjobEndpoint=localhost:8099 -PenvironmentType=LOOPBACK
>> cat /tmp/py-wordcount-direct* # to verify results.
>>
>> Loopback scenarios worked, however DOCKER scenarios did not. Opened
>> several Jiras to follow up:
>>
>> https://issues.apache.org/jira/browse/BEAM-7857
>> https://issues.apache.org/jira/browse/BEAM-7858
>> https://issues.apache.org/jira/browse/BEAM-7859
>> 
>>
>
> I commented on the bugs, and I think this is due to trying to use Docker
> mode with local files (a known issue).
>
>
>> The gradle targets that were required to run these tests are not present
>> in 2.13.0 branch, so I don't consider it a regression and still cast +1.
>>
>
> Agreed.
>
>
>> On Wed, Jul 31, 2019 at 11:31 AM Ismaël Mejía  wrote:
>>
>>> Oups Robert pointed to me that I have probably not counted correctly.
>>> There were indeed already 3 PMC +1 votes. Pablo, Robert and Ahmet.
>>> Please excuse me for the extra noise.
>>>
>>> On Wed, Jul 31, 2019 at 9:46 AM Ismaël Mejía  wrote:
>>> >
>>> > To complete the release we need to have at least three +1 binding
>>> > votes (votes from PMC members) as stated in [1]. So far we have only
>>> > 2.
>>> >
>>> > Thomas (and the others). The blog post PR is now open [2] please help
>>> > us add missing features or maybe to highlight the ones you consider
>>> > important in the PR comments.
>>> >
>>> > Here it is the missing +1 (binding). Validated SHAs+signatures,
>>> > beam-samples and one internal company project with the new jars.
>>> > Compared source file vs tagged git repo. Everything looks ok.
>>> >
>>> > [1] https://www.apache.org/foundation/voting.html#ReleaseVotes
>>> > [2] https://github.com/apache/beam/pull/9201/files
>>> >
>>> > On Wed, Jul 31, 2019 at 6:27 AM Anton Kedin  wrote:
>>> > >
>>> > > Ran various postcommits, validates runners, and nexmark against the
>>> release branch. All looks good so far.
>>> > >
>>> > > Will take another look at the docs/blog and the nexmark numbers
>>> tomorrow, but if nothing comes up I will close the vote tomorrow
>>> (Wednesday) by 6pm PST (= Thursday 01:00am UTC) since it's over 72hours
>>> since the vote has started and we have a number of +1s including PMC
>>> members and no -1s.
>>> > >
>>> > > Regards,
>>> > > Anton
>>> > >
>>> > > On Tue, Jul 30, 2019 at 8:13 PM Valentyn Tymofieiev <
>>> valen...@google.com> wrote:
>>> > >>
>>> > >> I also ran unit tests for Python 3.7 and they passed as well.
>>> Cython tests for python3.7 require  `apt-get install python3.7-dev`.
>>> > >>
>>> > >> On Wed, Jul 31, 2019 at 3:16 AM Pablo Estrada 
>>> wrote:
>>> > >>>
>>> > >>> +1
>>> > >>>
>>> > >>> I installed from source, and ran unit tests for Python in 2.7,
>>> 3.5, 3.6.
>>> > >>>
>>> > >>> Also ran a number of integration tests on Py 3.5 on Dataflow and
>>> DirectRunner.
>>> > >>> Best
>>> > >>> -P.
>>> > >>>
>>> > >>> On Tue, Jul 30, 2019 at 11:09 AM Hannah Jiang <
>>> hannahji...@google.com> wrote:
>>> > 
>>> >  I checked Py3 tests using .zip, mainly with direct runners, and
>>> everything looks good, so +1.
>>> > 
>>> >  On Tue, Jul 30, 2019 at 2:08 AM Robert Bradshaw <
>>> rober...@google.com> wrote:
>>> > >
>>> > > I checked all the artifact signatures and ran a couple test
>>> pipelines with the wheels (Py2 and Py3) and everything looked good to me,
>>> so +1.
>>> > >
>>> > > On Mon, Jul 29, 2019 at 8:29 PM Valentyn Tymofieiev <
>>> valen...@google.com> wrote:
>>> > >>
>>> > >> I have checked Python 3 batch and streaming quickstarts on
>>> Dataflow runner using .zip and wheel distributions. So far +1 from me.
>>> > >>
>>> > >> On Mon, Jul 29, 2019 at 7:53 PM Ahmet Altay 
>>> wrote:
>>> > >>>
>>> > >>> +1, validated python 2 quickstarts.
>>> > >>>
>>> > >>> On Fri, Jul 26, 2019 at 5:46 PM Ahmet Altay 
>>> wrote:
>>> > 
>>> >  To confirm, I manuall validated leader board on python. It is
>>> working.
>>> > 

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

[Robert Bradshaw]

On Wed, Jul 31, 2019 at 11:22 AM Valentyn Tymofieiev 
wrote:

> I have checked Portable Wordcount example on Flink and Spark on Python 2
> and Python 3.
>
> To do so, I had to checkout Beam from git repo, since using the source
> distribution does not include gradlew, and gradelw_orig did not work for
> me. Commands I ran:
>
> git checkout tags/v2.14.0-RC1
> ./gradlew :sdks:python:container:py3:docker
> ./gradlew :runners:flink:1.5:job-server:runShadow# Use  ./gradlew
> :runners:spark:job-server:runShadow for Spark
> ./gradlew :sdks:python:test-suites:portable:py35:portableWordCountBatch
>  -PjobEndpoint=localhost:8099 -PenvironmentType=LOOPBACK
> cat /tmp/py-wordcount-direct* # to verify results.
>
> Loopback scenarios worked, however DOCKER scenarios did not. Opened
> several Jiras to follow up:
>
> https://issues.apache.org/jira/browse/BEAM-7857
> https://issues.apache.org/jira/browse/BEAM-7858
> https://issues.apache.org/jira/browse/BEAM-7859
> 
>

I commented on the bugs, and I think this is due to trying to use Docker
mode with local files (a known issue).


> The gradle targets that were required to run these tests are not present
> in 2.13.0 branch, so I don't consider it a regression and still cast +1.
>

Agreed.


> On Wed, Jul 31, 2019 at 11:31 AM Ismaël Mejía  wrote:
>
>> Oups Robert pointed to me that I have probably not counted correctly.
>> There were indeed already 3 PMC +1 votes. Pablo, Robert and Ahmet.
>> Please excuse me for the extra noise.
>>
>> On Wed, Jul 31, 2019 at 9:46 AM Ismaël Mejía  wrote:
>> >
>> > To complete the release we need to have at least three +1 binding
>> > votes (votes from PMC members) as stated in [1]. So far we have only
>> > 2.
>> >
>> > Thomas (and the others). The blog post PR is now open [2] please help
>> > us add missing features or maybe to highlight the ones you consider
>> > important in the PR comments.
>> >
>> > Here it is the missing +1 (binding). Validated SHAs+signatures,
>> > beam-samples and one internal company project with the new jars.
>> > Compared source file vs tagged git repo. Everything looks ok.
>> >
>> > [1] https://www.apache.org/foundation/voting.html#ReleaseVotes
>> > [2] https://github.com/apache/beam/pull/9201/files
>> >
>> > On Wed, Jul 31, 2019 at 6:27 AM Anton Kedin  wrote:
>> > >
>> > > Ran various postcommits, validates runners, and nexmark against the
>> release branch. All looks good so far.
>> > >
>> > > Will take another look at the docs/blog and the nexmark numbers
>> tomorrow, but if nothing comes up I will close the vote tomorrow
>> (Wednesday) by 6pm PST (= Thursday 01:00am UTC) since it's over 72hours
>> since the vote has started and we have a number of +1s including PMC
>> members and no -1s.
>> > >
>> > > Regards,
>> > > Anton
>> > >
>> > > On Tue, Jul 30, 2019 at 8:13 PM Valentyn Tymofieiev <
>> valen...@google.com> wrote:
>> > >>
>> > >> I also ran unit tests for Python 3.7 and they passed as well. Cython
>> tests for python3.7 require  `apt-get install python3.7-dev`.
>> > >>
>> > >> On Wed, Jul 31, 2019 at 3:16 AM Pablo Estrada 
>> wrote:
>> > >>>
>> > >>> +1
>> > >>>
>> > >>> I installed from source, and ran unit tests for Python in 2.7, 3.5,
>> 3.6.
>> > >>>
>> > >>> Also ran a number of integration tests on Py 3.5 on Dataflow and
>> DirectRunner.
>> > >>> Best
>> > >>> -P.
>> > >>>
>> > >>> On Tue, Jul 30, 2019 at 11:09 AM Hannah Jiang <
>> hannahji...@google.com> wrote:
>> > 
>> >  I checked Py3 tests using .zip, mainly with direct runners, and
>> everything looks good, so +1.
>> > 
>> >  On Tue, Jul 30, 2019 at 2:08 AM Robert Bradshaw <
>> rober...@google.com> wrote:
>> > >
>> > > I checked all the artifact signatures and ran a couple test
>> pipelines with the wheels (Py2 and Py3) and everything looked good to me,
>> so +1.
>> > >
>> > > On Mon, Jul 29, 2019 at 8:29 PM Valentyn Tymofieiev <
>> valen...@google.com> wrote:
>> > >>
>> > >> I have checked Python 3 batch and streaming quickstarts on
>> Dataflow runner using .zip and wheel distributions. So far +1 from me.
>> > >>
>> > >> On Mon, Jul 29, 2019 at 7:53 PM Ahmet Altay 
>> wrote:
>> > >>>
>> > >>> +1, validated python 2 quickstarts.
>> > >>>
>> > >>> On Fri, Jul 26, 2019 at 5:46 PM Ahmet Altay 
>> wrote:
>> > 
>> >  To confirm, I manuall validated leader board on python. It is
>> working.
>> > 
>> >  On Fri, Jul 26, 2019 at 5:23 PM Yifan Zou 
>> wrote:
>> > >
>> > > AFAIK, there should not be any special prerequisites for
>> this. Things the script does including:
>> > > 1. download the python rc in zip
>> > > 2. start virtualenv and install the sdk.
>> > > 3. verify hash.
>> > > 4. config settings.xml and start a Java pubsub message
>> injector.
>> > > 5. run game examples and validate.
>> > >
>> > > Could you double 

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

[Valentyn Tymofieiev]

I have checked Portable Wordcount example on Flink and Spark on Python 2
and Python 3.

To do so, I had to checkout Beam from git repo, since using the source
distribution does not include gradlew, and gradelw_orig did not work for
me. Commands I ran:

git checkout tags/v2.14.0-RC1
./gradlew :sdks:python:container:py3:docker
./gradlew :runners:flink:1.5:job-server:runShadow# Use  ./gradlew
:runners:spark:job-server:runShadow for Spark
./gradlew :sdks:python:test-suites:portable:py35:portableWordCountBatch
 -PjobEndpoint=localhost:8099 -PenvironmentType=LOOPBACK
cat /tmp/py-wordcount-direct* # to verify results.

Loopback scenarios worked, however DOCKER scenarios did not. Opened several
Jiras to follow up:

https://issues.apache.org/jira/browse/BEAM-7857
https://issues.apache.org/jira/browse/BEAM-7858
https://issues.apache.org/jira/browse/BEAM-7859


The gradle targets that were required to run these tests are not present in
2.13.0 branch, so I don't consider it a regression and still cast +1.


On Wed, Jul 31, 2019 at 11:31 AM Ismaël Mejía  wrote:

> Oups Robert pointed to me that I have probably not counted correctly.
> There were indeed already 3 PMC +1 votes. Pablo, Robert and Ahmet.
> Please excuse me for the extra noise.
>
> On Wed, Jul 31, 2019 at 9:46 AM Ismaël Mejía  wrote:
> >
> > To complete the release we need to have at least three +1 binding
> > votes (votes from PMC members) as stated in [1]. So far we have only
> > 2.
> >
> > Thomas (and the others). The blog post PR is now open [2] please help
> > us add missing features or maybe to highlight the ones you consider
> > important in the PR comments.
> >
> > Here it is the missing +1 (binding). Validated SHAs+signatures,
> > beam-samples and one internal company project with the new jars.
> > Compared source file vs tagged git repo. Everything looks ok.
> >
> > [1] https://www.apache.org/foundation/voting.html#ReleaseVotes
> > [2] https://github.com/apache/beam/pull/9201/files
> >
> > On Wed, Jul 31, 2019 at 6:27 AM Anton Kedin  wrote:
> > >
> > > Ran various postcommits, validates runners, and nexmark against the
> release branch. All looks good so far.
> > >
> > > Will take another look at the docs/blog and the nexmark numbers
> tomorrow, but if nothing comes up I will close the vote tomorrow
> (Wednesday) by 6pm PST (= Thursday 01:00am UTC) since it's over 72hours
> since the vote has started and we have a number of +1s including PMC
> members and no -1s.
> > >
> > > Regards,
> > > Anton
> > >
> > > On Tue, Jul 30, 2019 at 8:13 PM Valentyn Tymofieiev <
> valen...@google.com> wrote:
> > >>
> > >> I also ran unit tests for Python 3.7 and they passed as well. Cython
> tests for python3.7 require  `apt-get install python3.7-dev`.
> > >>
> > >> On Wed, Jul 31, 2019 at 3:16 AM Pablo Estrada 
> wrote:
> > >>>
> > >>> +1
> > >>>
> > >>> I installed from source, and ran unit tests for Python in 2.7, 3.5,
> 3.6.
> > >>>
> > >>> Also ran a number of integration tests on Py 3.5 on Dataflow and
> DirectRunner.
> > >>> Best
> > >>> -P.
> > >>>
> > >>> On Tue, Jul 30, 2019 at 11:09 AM Hannah Jiang <
> hannahji...@google.com> wrote:
> > 
> >  I checked Py3 tests using .zip, mainly with direct runners, and
> everything looks good, so +1.
> > 
> >  On Tue, Jul 30, 2019 at 2:08 AM Robert Bradshaw <
> rober...@google.com> wrote:
> > >
> > > I checked all the artifact signatures and ran a couple test
> pipelines with the wheels (Py2 and Py3) and everything looked good to me,
> so +1.
> > >
> > > On Mon, Jul 29, 2019 at 8:29 PM Valentyn Tymofieiev <
> valen...@google.com> wrote:
> > >>
> > >> I have checked Python 3 batch and streaming quickstarts on
> Dataflow runner using .zip and wheel distributions. So far +1 from me.
> > >>
> > >> On Mon, Jul 29, 2019 at 7:53 PM Ahmet Altay 
> wrote:
> > >>>
> > >>> +1, validated python 2 quickstarts.
> > >>>
> > >>> On Fri, Jul 26, 2019 at 5:46 PM Ahmet Altay 
> wrote:
> > 
> >  To confirm, I manuall validated leader board on python. It is
> working.
> > 
> >  On Fri, Jul 26, 2019 at 5:23 PM Yifan Zou 
> wrote:
> > >
> > > AFAIK, there should not be any special prerequisites for this.
> Things the script does including:
> > > 1. download the python rc in zip
> > > 2. start virtualenv and install the sdk.
> > > 3. verify hash.
> > > 4. config settings.xml and start a Java pubsub message
> injector.
> > > 5. run game examples and validate.
> > >
> > > Could you double check if the sdk was installed properly (step
> 1&2)?
> > 
> > 
> >  I also guessing this is the case. Probably something earlier in
> the validation script did not run as expected.
> > 
> > >
> > >
> > >
> > > Yifan
> > >
> > > On Fri, Jul 26, 2019 at 

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

[Ismaël Mejía]

Oups Robert pointed to me that I have probably not counted correctly.
There were indeed already 3 PMC +1 votes. Pablo, Robert and Ahmet.
Please excuse me for the extra noise.

On Wed, Jul 31, 2019 at 9:46 AM Ismaël Mejía  wrote:
>
> To complete the release we need to have at least three +1 binding
> votes (votes from PMC members) as stated in [1]. So far we have only
> 2.
>
> Thomas (and the others). The blog post PR is now open [2] please help
> us add missing features or maybe to highlight the ones you consider
> important in the PR comments.
>
> Here it is the missing +1 (binding). Validated SHAs+signatures,
> beam-samples and one internal company project with the new jars.
> Compared source file vs tagged git repo. Everything looks ok.
>
> [1] https://www.apache.org/foundation/voting.html#ReleaseVotes
> [2] https://github.com/apache/beam/pull/9201/files
>
> On Wed, Jul 31, 2019 at 6:27 AM Anton Kedin  wrote:
> >
> > Ran various postcommits, validates runners, and nexmark against the release 
> > branch. All looks good so far.
> >
> > Will take another look at the docs/blog and the nexmark numbers tomorrow, 
> > but if nothing comes up I will close the vote tomorrow (Wednesday) by 6pm 
> > PST (= Thursday 01:00am UTC) since it's over 72hours since the vote has 
> > started and we have a number of +1s including PMC members and no -1s.
> >
> > Regards,
> > Anton
> >
> > On Tue, Jul 30, 2019 at 8:13 PM Valentyn Tymofieiev  
> > wrote:
> >>
> >> I also ran unit tests for Python 3.7 and they passed as well. Cython tests 
> >> for python3.7 require  `apt-get install python3.7-dev`.
> >>
> >> On Wed, Jul 31, 2019 at 3:16 AM Pablo Estrada  wrote:
> >>>
> >>> +1
> >>>
> >>> I installed from source, and ran unit tests for Python in 2.7, 3.5, 3.6.
> >>>
> >>> Also ran a number of integration tests on Py 3.5 on Dataflow and 
> >>> DirectRunner.
> >>> Best
> >>> -P.
> >>>
> >>> On Tue, Jul 30, 2019 at 11:09 AM Hannah Jiang  
> >>> wrote:
> 
>  I checked Py3 tests using .zip, mainly with direct runners, and 
>  everything looks good, so +1.
> 
>  On Tue, Jul 30, 2019 at 2:08 AM Robert Bradshaw  
>  wrote:
> >
> > I checked all the artifact signatures and ran a couple test pipelines 
> > with the wheels (Py2 and Py3) and everything looked good to me, so +1.
> >
> > On Mon, Jul 29, 2019 at 8:29 PM Valentyn Tymofieiev 
> >  wrote:
> >>
> >> I have checked Python 3 batch and streaming quickstarts on Dataflow 
> >> runner using .zip and wheel distributions. So far +1 from me.
> >>
> >> On Mon, Jul 29, 2019 at 7:53 PM Ahmet Altay  wrote:
> >>>
> >>> +1, validated python 2 quickstarts.
> >>>
> >>> On Fri, Jul 26, 2019 at 5:46 PM Ahmet Altay  wrote:
> 
>  To confirm, I manuall validated leader board on python. It is 
>  working.
> 
>  On Fri, Jul 26, 2019 at 5:23 PM Yifan Zou  
>  wrote:
> >
> > AFAIK, there should not be any special prerequisites for this. 
> > Things the script does including:
> > 1. download the python rc in zip
> > 2. start virtualenv and install the sdk.
> > 3. verify hash.
> > 4. config settings.xml and start a Java pubsub message injector.
> > 5. run game examples and validate.
> >
> > Could you double check if the sdk was installed properly (step 1&2)?
> 
> 
>  I also guessing this is the case. Probably something earlier in the 
>  validation script did not run as expected.
> 
> >
> >
> >
> > Yifan
> >
> > On Fri, Jul 26, 2019 at 2:38 PM Anton Kedin  
> > wrote:
> >>
> >> Validation script fails for me when I try to run [1] python 
> >> leaderboard with direct runner:
> >>
> >> ```
> >> *
> >> * Running Python Leaderboard with DirectRunner
> >> *
> >> /usr/bin/python: No module named apache_beam.examples.complete.game
> >> ```
> >>
> >> If someone has more context, what are the prerequisites for this 
> >> step? How does it look up the module?
> >>
> >> [1] 
> >> https://github.com/apache/beam/blob/master/release/src/main/scripts/run_rc_validation.sh#L424
> >>
> >> Regards,
> >> Anton
> >>
> >> On Fri, Jul 26, 2019 at 10:23 AM Anton Kedin  
> >> wrote:
> >>>
> >>> Cool, will make the post and will update the release guide as 
> >>> well then
> >>>
> >>> On Fri, Jul 26, 2019 at 10:20 AM Chad Dombrova 
> >>>  wrote:
> >
> > I think the release guide needs to be updated to remove the 
> > optionality of blog creation and avoid confusion. 

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

[Ismaël Mejía]

To complete the release we need to have at least three +1 binding
votes (votes from PMC members) as stated in [1]. So far we have only
2.

Thomas (and the others). The blog post PR is now open [2] please help
us add missing features or maybe to highlight the ones you consider
important in the PR comments.

Here it is the missing +1 (binding). Validated SHAs+signatures,
beam-samples and one internal company project with the new jars.
Compared source file vs tagged git repo. Everything looks ok.

[1] https://www.apache.org/foundation/voting.html#ReleaseVotes
[2] https://github.com/apache/beam/pull/9201/files

On Wed, Jul 31, 2019 at 6:27 AM Anton Kedin  wrote:
>
> Ran various postcommits, validates runners, and nexmark against the release 
> branch. All looks good so far.
>
> Will take another look at the docs/blog and the nexmark numbers tomorrow, but 
> if nothing comes up I will close the vote tomorrow (Wednesday) by 6pm PST (= 
> Thursday 01:00am UTC) since it's over 72hours since the vote has started and 
> we have a number of +1s including PMC members and no -1s.
>
> Regards,
> Anton
>
> On Tue, Jul 30, 2019 at 8:13 PM Valentyn Tymofieiev  
> wrote:
>>
>> I also ran unit tests for Python 3.7 and they passed as well. Cython tests 
>> for python3.7 require  `apt-get install python3.7-dev`.
>>
>> On Wed, Jul 31, 2019 at 3:16 AM Pablo Estrada  wrote:
>>>
>>> +1
>>>
>>> I installed from source, and ran unit tests for Python in 2.7, 3.5, 3.6.
>>>
>>> Also ran a number of integration tests on Py 3.5 on Dataflow and 
>>> DirectRunner.
>>> Best
>>> -P.
>>>
>>> On Tue, Jul 30, 2019 at 11:09 AM Hannah Jiang  
>>> wrote:

 I checked Py3 tests using .zip, mainly with direct runners, and everything 
 looks good, so +1.

 On Tue, Jul 30, 2019 at 2:08 AM Robert Bradshaw  
 wrote:
>
> I checked all the artifact signatures and ran a couple test pipelines 
> with the wheels (Py2 and Py3) and everything looked good to me, so +1.
>
> On Mon, Jul 29, 2019 at 8:29 PM Valentyn Tymofieiev  
> wrote:
>>
>> I have checked Python 3 batch and streaming quickstarts on Dataflow 
>> runner using .zip and wheel distributions. So far +1 from me.
>>
>> On Mon, Jul 29, 2019 at 7:53 PM Ahmet Altay  wrote:
>>>
>>> +1, validated python 2 quickstarts.
>>>
>>> On Fri, Jul 26, 2019 at 5:46 PM Ahmet Altay  wrote:

 To confirm, I manuall validated leader board on python. It is working.

 On Fri, Jul 26, 2019 at 5:23 PM Yifan Zou  wrote:
>
> AFAIK, there should not be any special prerequisites for this. Things 
> the script does including:
> 1. download the python rc in zip
> 2. start virtualenv and install the sdk.
> 3. verify hash.
> 4. config settings.xml and start a Java pubsub message injector.
> 5. run game examples and validate.
>
> Could you double check if the sdk was installed properly (step 1&2)?


 I also guessing this is the case. Probably something earlier in the 
 validation script did not run as expected.

>
>
>
> Yifan
>
> On Fri, Jul 26, 2019 at 2:38 PM Anton Kedin  wrote:
>>
>> Validation script fails for me when I try to run [1] python 
>> leaderboard with direct runner:
>>
>> ```
>> *
>> * Running Python Leaderboard with DirectRunner
>> *
>> /usr/bin/python: No module named apache_beam.examples.complete.game
>> ```
>>
>> If someone has more context, what are the prerequisites for this 
>> step? How does it look up the module?
>>
>> [1] 
>> https://github.com/apache/beam/blob/master/release/src/main/scripts/run_rc_validation.sh#L424
>>
>> Regards,
>> Anton
>>
>> On Fri, Jul 26, 2019 at 10:23 AM Anton Kedin  
>> wrote:
>>>
>>> Cool, will make the post and will update the release guide as well 
>>> then
>>>
>>> On Fri, Jul 26, 2019 at 10:20 AM Chad Dombrova  
>>> wrote:
>
> I think the release guide needs to be updated to remove the 
> optionality of blog creation and avoid confusion. Thanks for 
> pointing that out.


 +1

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

[Anton Kedin]

Ran various postcommits, validates runners, and nexmark against the release
branch. All looks good so far.

Will take another look at the docs/blog and the nexmark numbers tomorrow,
but if nothing comes up I will close the vote tomorrow (Wednesday) by 6pm
PST (= Thursday 01:00am UTC) since it's over 72hours since the vote has
started and we have a number of +1s including PMC members and no -1s.

Regards,
Anton

On Tue, Jul 30, 2019 at 8:13 PM Valentyn Tymofieiev 
wrote:

> I also ran unit tests for Python 3.7 and they passed as well. Cython tests
> for python3.7 require  `apt-get install python3.7-dev`.
>
> On Wed, Jul 31, 2019 at 3:16 AM Pablo Estrada  wrote:
>
>> +1
>>
>> I installed from source, and ran unit tests for Python in 2.7, 3.5, 3.6.
>>
>> Also ran a number of integration tests on Py 3.5 on Dataflow and
>> DirectRunner.
>> Best
>> -P.
>>
>> On Tue, Jul 30, 2019 at 11:09 AM Hannah Jiang 
>> wrote:
>>
>>> I checked Py3 tests using .zip, mainly with direct runners, and
>>> everything looks good, so +1.
>>>
>>> On Tue, Jul 30, 2019 at 2:08 AM Robert Bradshaw 
>>> wrote:
>>>
 I checked all the artifact signatures and ran a couple test pipelines
 with the wheels (Py2 and Py3) and everything looked good to me, so +1.

 On Mon, Jul 29, 2019 at 8:29 PM Valentyn Tymofieiev <
 valen...@google.com> wrote:

> I have checked Python 3 batch and streaming quickstarts on Dataflow
> runner using .zip and wheel distributions. So far +1 from me.
>
> On Mon, Jul 29, 2019 at 7:53 PM Ahmet Altay  wrote:
>
>> +1, validated python 2 quickstarts.
>>
>> On Fri, Jul 26, 2019 at 5:46 PM Ahmet Altay  wrote:
>>
>>> To confirm, I manuall validated leader board on python. It is
>>> working.
>>>
>>> On Fri, Jul 26, 2019 at 5:23 PM Yifan Zou 
>>> wrote:
>>>
 AFAIK, there should not be any special prerequisites for this.
 Things the script does including:
 1. download the python rc in zip
 2. start virtualenv and install the sdk.
 3. verify hash.
 4. config settings.xml and start a Java pubsub message injector.
 5. run game examples and validate.

 Could you double check if the sdk was installed properly (step 1&2)?

>>>
>>> I also guessing this is the case. Probably something earlier in the
>>> validation script did not run as expected.
>>>
>>>


>>> Yifan

 On Fri, Jul 26, 2019 at 2:38 PM Anton Kedin 
 wrote:

> Validation script fails for me when I try to run [1] python
> leaderboard with direct runner:
>
> ```
> *
> * Running Python Leaderboard with DirectRunner
> *
> /usr/bin/python: No module named apache_beam.examples.complete.game
> ```
>
> If someone has more context, what are the prerequisites for this
> step? How does it look up the module?
>
> [1]
> https://github.com/apache/beam/blob/master/release/src/main/scripts/run_rc_validation.sh#L424
>
> Regards,
> Anton
>
> On Fri, Jul 26, 2019 at 10:23 AM Anton Kedin 
> wrote:
>
>> Cool, will make the post and will update the release guide as
>> well then
>>
>> On Fri, Jul 26, 2019 at 10:20 AM Chad Dombrova 
>> wrote:
>>
>>> I think the release guide needs to be updated to remove the
 optionality of blog creation and avoid confusion. Thanks for 
 pointing that
 out.

>>>
>>> +1
>>>
>>>

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

[Valentyn Tymofieiev]

I also ran unit tests for Python 3.7 and they passed as well. Cython tests
for python3.7 require  `apt-get install python3.7-dev`.

On Wed, Jul 31, 2019 at 3:16 AM Pablo Estrada  wrote:

> +1
>
> I installed from source, and ran unit tests for Python in 2.7, 3.5, 3.6.
>
> Also ran a number of integration tests on Py 3.5 on Dataflow and
> DirectRunner.
> Best
> -P.
>
> On Tue, Jul 30, 2019 at 11:09 AM Hannah Jiang 
> wrote:
>
>> I checked Py3 tests using .zip, mainly with direct runners, and
>> everything looks good, so +1.
>>
>> On Tue, Jul 30, 2019 at 2:08 AM Robert Bradshaw 
>> wrote:
>>
>>> I checked all the artifact signatures and ran a couple test pipelines
>>> with the wheels (Py2 and Py3) and everything looked good to me, so +1.
>>>
>>> On Mon, Jul 29, 2019 at 8:29 PM Valentyn Tymofieiev 
>>> wrote:
>>>
 I have checked Python 3 batch and streaming quickstarts on Dataflow
 runner using .zip and wheel distributions. So far +1 from me.

 On Mon, Jul 29, 2019 at 7:53 PM Ahmet Altay  wrote:

> +1, validated python 2 quickstarts.
>
> On Fri, Jul 26, 2019 at 5:46 PM Ahmet Altay  wrote:
>
>> To confirm, I manuall validated leader board on python. It is working.
>>
>> On Fri, Jul 26, 2019 at 5:23 PM Yifan Zou 
>> wrote:
>>
>>> AFAIK, there should not be any special prerequisites for this.
>>> Things the script does including:
>>> 1. download the python rc in zip
>>> 2. start virtualenv and install the sdk.
>>> 3. verify hash.
>>> 4. config settings.xml and start a Java pubsub message injector.
>>> 5. run game examples and validate.
>>>
>>> Could you double check if the sdk was installed properly (step 1&2)?
>>>
>>
>> I also guessing this is the case. Probably something earlier in the
>> validation script did not run as expected.
>>
>>
>>>
>>>
>> Yifan
>>>
>>> On Fri, Jul 26, 2019 at 2:38 PM Anton Kedin 
>>> wrote:
>>>
 Validation script fails for me when I try to run [1] python
 leaderboard with direct runner:

 ```
 *
 * Running Python Leaderboard with DirectRunner
 *
 /usr/bin/python: No module named apache_beam.examples.complete.game
 ```

 If someone has more context, what are the prerequisites for this
 step? How does it look up the module?

 [1]
 https://github.com/apache/beam/blob/master/release/src/main/scripts/run_rc_validation.sh#L424

 Regards,
 Anton

 On Fri, Jul 26, 2019 at 10:23 AM Anton Kedin 
 wrote:

> Cool, will make the post and will update the release guide as well
> then
>
> On Fri, Jul 26, 2019 at 10:20 AM Chad Dombrova 
> wrote:
>
>> I think the release guide needs to be updated to remove the
>>> optionality of blog creation and avoid confusion. Thanks for 
>>> pointing that
>>> out.
>>>
>>
>> +1
>>
>>

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

[Pablo Estrada]

+1

I installed from source, and ran unit tests for Python in 2.7, 3.5, 3.6.

Also ran a number of integration tests on Py 3.5 on Dataflow and
DirectRunner.
Best
-P.

On Tue, Jul 30, 2019 at 11:09 AM Hannah Jiang 
wrote:

> I checked Py3 tests using .zip, mainly with direct runners, and everything
> looks good, so +1.
>
> On Tue, Jul 30, 2019 at 2:08 AM Robert Bradshaw 
> wrote:
>
>> I checked all the artifact signatures and ran a couple test pipelines
>> with the wheels (Py2 and Py3) and everything looked good to me, so +1.
>>
>> On Mon, Jul 29, 2019 at 8:29 PM Valentyn Tymofieiev 
>> wrote:
>>
>>> I have checked Python 3 batch and streaming quickstarts on Dataflow
>>> runner using .zip and wheel distributions. So far +1 from me.
>>>
>>> On Mon, Jul 29, 2019 at 7:53 PM Ahmet Altay  wrote:
>>>
 +1, validated python 2 quickstarts.

 On Fri, Jul 26, 2019 at 5:46 PM Ahmet Altay  wrote:

> To confirm, I manuall validated leader board on python. It is working.
>
> On Fri, Jul 26, 2019 at 5:23 PM Yifan Zou  wrote:
>
>> AFAIK, there should not be any special prerequisites for this. Things
>> the script does including:
>> 1. download the python rc in zip
>> 2. start virtualenv and install the sdk.
>> 3. verify hash.
>> 4. config settings.xml and start a Java pubsub message injector.
>> 5. run game examples and validate.
>>
>> Could you double check if the sdk was installed properly (step 1&2)?
>>
>
> I also guessing this is the case. Probably something earlier in the
> validation script did not run as expected.
>
>
>>
>>
> Yifan
>>
>> On Fri, Jul 26, 2019 at 2:38 PM Anton Kedin  wrote:
>>
>>> Validation script fails for me when I try to run [1] python
>>> leaderboard with direct runner:
>>>
>>> ```
>>> *
>>> * Running Python Leaderboard with DirectRunner
>>> *
>>> /usr/bin/python: No module named apache_beam.examples.complete.game
>>> ```
>>>
>>> If someone has more context, what are the prerequisites for this
>>> step? How does it look up the module?
>>>
>>> [1]
>>> https://github.com/apache/beam/blob/master/release/src/main/scripts/run_rc_validation.sh#L424
>>>
>>> Regards,
>>> Anton
>>>
>>> On Fri, Jul 26, 2019 at 10:23 AM Anton Kedin 
>>> wrote:
>>>
 Cool, will make the post and will update the release guide as well
 then

 On Fri, Jul 26, 2019 at 10:20 AM Chad Dombrova 
 wrote:

> I think the release guide needs to be updated to remove the
>> optionality of blog creation and avoid confusion. Thanks for 
>> pointing that
>> out.
>>
>
> +1
>
>

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

[Hannah Jiang]

I checked Py3 tests using .zip, mainly with direct runners, and everything
looks good, so +1.

On Tue, Jul 30, 2019 at 2:08 AM Robert Bradshaw  wrote:

> I checked all the artifact signatures and ran a couple test pipelines with
> the wheels (Py2 and Py3) and everything looked good to me, so +1.
>
> On Mon, Jul 29, 2019 at 8:29 PM Valentyn Tymofieiev 
> wrote:
>
>> I have checked Python 3 batch and streaming quickstarts on Dataflow
>> runner using .zip and wheel distributions. So far +1 from me.
>>
>> On Mon, Jul 29, 2019 at 7:53 PM Ahmet Altay  wrote:
>>
>>> +1, validated python 2 quickstarts.
>>>
>>> On Fri, Jul 26, 2019 at 5:46 PM Ahmet Altay  wrote:
>>>
 To confirm, I manuall validated leader board on python. It is working.

 On Fri, Jul 26, 2019 at 5:23 PM Yifan Zou  wrote:

> AFAIK, there should not be any special prerequisites for this. Things
> the script does including:
> 1. download the python rc in zip
> 2. start virtualenv and install the sdk.
> 3. verify hash.
> 4. config settings.xml and start a Java pubsub message injector.
> 5. run game examples and validate.
>
> Could you double check if the sdk was installed properly (step 1&2)?
>

 I also guessing this is the case. Probably something earlier in the
 validation script did not run as expected.


>
>
 Yifan
>
> On Fri, Jul 26, 2019 at 2:38 PM Anton Kedin  wrote:
>
>> Validation script fails for me when I try to run [1] python
>> leaderboard with direct runner:
>>
>> ```
>> *
>> * Running Python Leaderboard with DirectRunner
>> *
>> /usr/bin/python: No module named apache_beam.examples.complete.game
>> ```
>>
>> If someone has more context, what are the prerequisites for this
>> step? How does it look up the module?
>>
>> [1]
>> https://github.com/apache/beam/blob/master/release/src/main/scripts/run_rc_validation.sh#L424
>>
>> Regards,
>> Anton
>>
>> On Fri, Jul 26, 2019 at 10:23 AM Anton Kedin 
>> wrote:
>>
>>> Cool, will make the post and will update the release guide as well
>>> then
>>>
>>> On Fri, Jul 26, 2019 at 10:20 AM Chad Dombrova 
>>> wrote:
>>>
 I think the release guide needs to be updated to remove the
> optionality of blog creation and avoid confusion. Thanks for pointing 
> that
> out.
>

 +1

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

[Robert Bradshaw]

I checked all the artifact signatures and ran a couple test pipelines with
the wheels (Py2 and Py3) and everything looked good to me, so +1.

On Mon, Jul 29, 2019 at 8:29 PM Valentyn Tymofieiev 
wrote:

> I have checked Python 3 batch and streaming quickstarts on Dataflow runner
> using .zip and wheel distributions. So far +1 from me.
>
> On Mon, Jul 29, 2019 at 7:53 PM Ahmet Altay  wrote:
>
>> +1, validated python 2 quickstarts.
>>
>> On Fri, Jul 26, 2019 at 5:46 PM Ahmet Altay  wrote:
>>
>>> To confirm, I manuall validated leader board on python. It is working.
>>>
>>> On Fri, Jul 26, 2019 at 5:23 PM Yifan Zou  wrote:
>>>
 AFAIK, there should not be any special prerequisites for this. Things
 the script does including:
 1. download the python rc in zip
 2. start virtualenv and install the sdk.
 3. verify hash.
 4. config settings.xml and start a Java pubsub message injector.
 5. run game examples and validate.

 Could you double check if the sdk was installed properly (step 1&2)?

>>>
>>> I also guessing this is the case. Probably something earlier in the
>>> validation script did not run as expected.
>>>
>>>


>>> Yifan

 On Fri, Jul 26, 2019 at 2:38 PM Anton Kedin  wrote:

> Validation script fails for me when I try to run [1] python
> leaderboard with direct runner:
>
> ```
> *
> * Running Python Leaderboard with DirectRunner
> *
> /usr/bin/python: No module named apache_beam.examples.complete.game
> ```
>
> If someone has more context, what are the prerequisites for this step?
> How does it look up the module?
>
> [1]
> https://github.com/apache/beam/blob/master/release/src/main/scripts/run_rc_validation.sh#L424
>
> Regards,
> Anton
>
> On Fri, Jul 26, 2019 at 10:23 AM Anton Kedin  wrote:
>
>> Cool, will make the post and will update the release guide as well
>> then
>>
>> On Fri, Jul 26, 2019 at 10:20 AM Chad Dombrova 
>> wrote:
>>
>>> I think the release guide needs to be updated to remove the
 optionality of blog creation and avoid confusion. Thanks for pointing 
 that
 out.

>>>
>>> +1
>>>
>>>

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

[Valentyn Tymofieiev]

I have checked Python 3 batch and streaming quickstarts on Dataflow runner
using .zip and wheel distributions. So far +1 from me.

On Mon, Jul 29, 2019 at 7:53 PM Ahmet Altay  wrote:

> +1, validated python 2 quickstarts.
>
> On Fri, Jul 26, 2019 at 5:46 PM Ahmet Altay  wrote:
>
>> To confirm, I manuall validated leader board on python. It is working.
>>
>> On Fri, Jul 26, 2019 at 5:23 PM Yifan Zou  wrote:
>>
>>> AFAIK, there should not be any special prerequisites for this. Things
>>> the script does including:
>>> 1. download the python rc in zip
>>> 2. start virtualenv and install the sdk.
>>> 3. verify hash.
>>> 4. config settings.xml and start a Java pubsub message injector.
>>> 5. run game examples and validate.
>>>
>>> Could you double check if the sdk was installed properly (step 1&2)?
>>>
>>
>> I also guessing this is the case. Probably something earlier in the
>> validation script did not run as expected.
>>
>>
>>>
>>>
>> Yifan
>>>
>>> On Fri, Jul 26, 2019 at 2:38 PM Anton Kedin  wrote:
>>>
 Validation script fails for me when I try to run [1] python leaderboard
 with direct runner:

 ```
 *
 * Running Python Leaderboard with DirectRunner
 *
 /usr/bin/python: No module named apache_beam.examples.complete.game
 ```

 If someone has more context, what are the prerequisites for this step?
 How does it look up the module?

 [1]
 https://github.com/apache/beam/blob/master/release/src/main/scripts/run_rc_validation.sh#L424

 Regards,
 Anton

 On Fri, Jul 26, 2019 at 10:23 AM Anton Kedin  wrote:

> Cool, will make the post and will update the release guide as well then
>
> On Fri, Jul 26, 2019 at 10:20 AM Chad Dombrova 
> wrote:
>
>> I think the release guide needs to be updated to remove the
>>> optionality of blog creation and avoid confusion. Thanks for pointing 
>>> that
>>> out.
>>>
>>
>> +1
>>
>>

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

[Ahmet Altay]

+1, validated python 2 quickstarts.

On Fri, Jul 26, 2019 at 5:46 PM Ahmet Altay  wrote:

> To confirm, I manuall validated leader board on python. It is working.
>
> On Fri, Jul 26, 2019 at 5:23 PM Yifan Zou  wrote:
>
>> AFAIK, there should not be any special prerequisites for this. Things the
>> script does including:
>> 1. download the python rc in zip
>> 2. start virtualenv and install the sdk.
>> 3. verify hash.
>> 4. config settings.xml and start a Java pubsub message injector.
>> 5. run game examples and validate.
>>
>> Could you double check if the sdk was installed properly (step 1&2)?
>>
>
> I also guessing this is the case. Probably something earlier in the
> validation script did not run as expected.
>
>
>>
>>
> Yifan
>>
>> On Fri, Jul 26, 2019 at 2:38 PM Anton Kedin  wrote:
>>
>>> Validation script fails for me when I try to run [1] python leaderboard
>>> with direct runner:
>>>
>>> ```
>>> *
>>> * Running Python Leaderboard with DirectRunner
>>> *
>>> /usr/bin/python: No module named apache_beam.examples.complete.game
>>> ```
>>>
>>> If someone has more context, what are the prerequisites for this step?
>>> How does it look up the module?
>>>
>>> [1]
>>> https://github.com/apache/beam/blob/master/release/src/main/scripts/run_rc_validation.sh#L424
>>>
>>> Regards,
>>> Anton
>>>
>>> On Fri, Jul 26, 2019 at 10:23 AM Anton Kedin  wrote:
>>>
 Cool, will make the post and will update the release guide as well then

 On Fri, Jul 26, 2019 at 10:20 AM Chad Dombrova 
 wrote:

> I think the release guide needs to be updated to remove the
>> optionality of blog creation and avoid confusion. Thanks for pointing 
>> that
>> out.
>>
>
> +1
>
>

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

[Ahmet Altay]

To confirm, I manuall validated leader board on python. It is working.

On Fri, Jul 26, 2019 at 5:23 PM Yifan Zou  wrote:

> AFAIK, there should not be any special prerequisites for this. Things the
> script does including:
> 1. download the python rc in zip
> 2. start virtualenv and install the sdk.
> 3. verify hash.
> 4. config settings.xml and start a Java pubsub message injector.
> 5. run game examples and validate.
>
> Could you double check if the sdk was installed properly (step 1&2)?
>

I also guessing this is the case. Probably something earlier in the
validation script did not run as expected.


>
>
Yifan
>
> On Fri, Jul 26, 2019 at 2:38 PM Anton Kedin  wrote:
>
>> Validation script fails for me when I try to run [1] python leaderboard
>> with direct runner:
>>
>> ```
>> *
>> * Running Python Leaderboard with DirectRunner
>> *
>> /usr/bin/python: No module named apache_beam.examples.complete.game
>> ```
>>
>> If someone has more context, what are the prerequisites for this step?
>> How does it look up the module?
>>
>> [1]
>> https://github.com/apache/beam/blob/master/release/src/main/scripts/run_rc_validation.sh#L424
>>
>> Regards,
>> Anton
>>
>> On Fri, Jul 26, 2019 at 10:23 AM Anton Kedin  wrote:
>>
>>> Cool, will make the post and will update the release guide as well then
>>>
>>> On Fri, Jul 26, 2019 at 10:20 AM Chad Dombrova 
>>> wrote:
>>>
 I think the release guide needs to be updated to remove the optionality
> of blog creation and avoid confusion. Thanks for pointing that out.
>

 +1

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

[Yifan Zou]

AFAIK, there should not be any special prerequisites for this. Things the
script does including:
1. download the python rc in zip
2. start virtualenv and install the sdk.
3. verify hash.
4. config settings.xml and start a Java pubsub message injector.
5. run game examples and validate.

Could you double check if the sdk was installed properly (step 1&2)?

Yifan

On Fri, Jul 26, 2019 at 2:38 PM Anton Kedin  wrote:

> Validation script fails for me when I try to run [1] python leaderboard
> with direct runner:
>
> ```
> *
> * Running Python Leaderboard with DirectRunner
> *
> /usr/bin/python: No module named apache_beam.examples.complete.game
> ```
>
> If someone has more context, what are the prerequisites for this step? How
> does it look up the module?
>
> [1]
> https://github.com/apache/beam/blob/master/release/src/main/scripts/run_rc_validation.sh#L424
>
> Regards,
> Anton
>
> On Fri, Jul 26, 2019 at 10:23 AM Anton Kedin  wrote:
>
>> Cool, will make the post and will update the release guide as well then
>>
>> On Fri, Jul 26, 2019 at 10:20 AM Chad Dombrova  wrote:
>>
>>> I think the release guide needs to be updated to remove the optionality
 of blog creation and avoid confusion. Thanks for pointing that out.

>>>
>>> +1
>>>
>>>

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

[Anton Kedin]

Cool, will make the post and will update the release guide as well then

On Fri, Jul 26, 2019 at 10:20 AM Chad Dombrova  wrote:

> I think the release guide needs to be updated to remove the optionality of
>> blog creation and avoid confusion. Thanks for pointing that out.
>>
>
> +1
>
>

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

[Chad Dombrova]

>
> I think the release guide needs to be updated to remove the optionality of
> blog creation and avoid confusion. Thanks for pointing that out.
>

+1

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

[Thomas Weise]

A quick look over the JIRA release notes reveals new features and important
improvements that call to be announced.

I think the release guide needs to be updated to remove the optionality of
blog creation and avoid confusion. Thanks for pointing that out.

On Fri, Jul 26, 2019 at 9:53 AM Anton Kedin  wrote:

> Hi Thomas, I haven't made it. I read that step of the guide as optional
> ("..if needed for this particular release..."). I am not sure if anything
> specific needs to be announced or highlighted for 2.14. I can go over the
> closed Jiras and create a blog post if it's expected.
>
> Regards,
> Anton
>
> On Fri, Jul 26, 2019 at 9:38 AM Thomas Weise  wrote:
>
>> Hi Anton,
>>
>> Thanks for working on the release.
>>
>> I don't find the release blog in https://github.com/apache/beam/pull/9157 or
>> elsewhere?
>>
>> This should be part of the release candidate [1] and I wonder why we keep
>> on missing it in RCs. Is there something that needs be be fixed in [1]?
>>
>> The reason why I now check for this as one of the first items is that we
>> traditionally have done poorly communicating releases to users when this is
>> actually very important. The blog needs many eyes to make sure we capture
>> what matters in a way that makes sense to users.
>>
>> Thomas
>>
>>
>>
>>
>>
>>
>> [1]
>> https://beam.apache.org/contribute/release-guide/#write-the-beam-blog-post-and-create-a-pull-request
>>
>>
>>
>> On Thu, Jul 25, 2019 at 4:25 PM Rui Wang  wrote:
>>
>>> Tried to verify RC1 by running Nexmark on Dataflow but found it's broken
>>> (at least based commands from Running+Nexmark
>>> ).
>>> Will try to debug it and rerun the process.
>>>
>>>
>>> -Rui
>>>
>>> On Thu, Jul 25, 2019 at 2:39 PM Anton Kedin  wrote:
>>>
 Hi everyone,
 Please review and vote on the release candidate #3 for the version
 2.14.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
 89E2FFCAE7E99CF6E6827CFEF7349F2310FFB193 [3],
 * all artifacts to be deployed to the Maven Central Repository [4],
 * source code tag "v2.14.0-RC1" [5], [6]
 * website pull request listing the release [7], publishing the API
 reference manual [8].
 * Python artifacts are deployed along with the source release to the
 dist.apache.org [2].
 * Validation sheet with a tab for 2.14.0 release to help with
 validation [9].

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

 Thanks,
 Anton

 [1]
 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527=12345431
 [2] https://dist.apache.org/repos/dist/dev/beam/2.14.0/
 [3] https://dist.apache.org/repos/dist/release/beam/KEYS
 [4]
 https://repository.apache.org/content/repositories/orgapachebeam-1080/
 [5] https://github.com/apache/beam/tree/v2.14.0-RC1
 [6] https://github.com/apache/beam/tags
 [7] https://github.com/apache/beam/pull/9157
 [8] https://github.com/apache/beam-site/pull/591/
 [9] https://s.apache.org/beam-release-validation#gid=1082148452

>>>

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

[Anton Kedin]

Hi Thomas, I haven't made it. I read that step of the guide as optional ("..if
needed for this particular release..."). I am not sure if anything specific
needs to be announced or highlighted for 2.14. I can go over the closed
Jiras and create a blog post if it's expected.

Regards,
Anton

On Fri, Jul 26, 2019 at 9:38 AM Thomas Weise  wrote:

> Hi Anton,
>
> Thanks for working on the release.
>
> I don't find the release blog in https://github.com/apache/beam/pull/9157 or
> elsewhere?
>
> This should be part of the release candidate [1] and I wonder why we keep
> on missing it in RCs. Is there something that needs be be fixed in [1]?
>
> The reason why I now check for this as one of the first items is that we
> traditionally have done poorly communicating releases to users when this is
> actually very important. The blog needs many eyes to make sure we capture
> what matters in a way that makes sense to users.
>
> Thomas
>
>
>
>
>
>
> [1]
> https://beam.apache.org/contribute/release-guide/#write-the-beam-blog-post-and-create-a-pull-request
>
>
>
> On Thu, Jul 25, 2019 at 4:25 PM Rui Wang  wrote:
>
>> Tried to verify RC1 by running Nexmark on Dataflow but found it's broken
>> (at least based commands from Running+Nexmark
>> ).
>> Will try to debug it and rerun the process.
>>
>>
>> -Rui
>>
>> On Thu, Jul 25, 2019 at 2:39 PM Anton Kedin  wrote:
>>
>>> Hi everyone,
>>> Please review and vote on the release candidate #3 for the version
>>> 2.14.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
>>> 89E2FFCAE7E99CF6E6827CFEF7349F2310FFB193 [3],
>>> * all artifacts to be deployed to the Maven Central Repository [4],
>>> * source code tag "v2.14.0-RC1" [5], [6]
>>> * website pull request listing the release [7], publishing the API
>>> reference manual [8].
>>> * Python artifacts are deployed along with the source release to the
>>> dist.apache.org [2].
>>> * Validation sheet with a tab for 2.14.0 release to help with validation
>>> [9].
>>>
>>> The vote will be open for at least 72 hours. It is adopted by majority
>>> approval, with at least 3 PMC affirmative votes.
>>>
>>> Thanks,
>>> Anton
>>>
>>> [1]
>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527=12345431
>>> [2] https://dist.apache.org/repos/dist/dev/beam/2.14.0/
>>> [3] https://dist.apache.org/repos/dist/release/beam/KEYS
>>> [4]
>>> https://repository.apache.org/content/repositories/orgapachebeam-1080/
>>> [5] https://github.com/apache/beam/tree/v2.14.0-RC1
>>> [6] https://github.com/apache/beam/tags
>>> [7] https://github.com/apache/beam/pull/9157
>>> [8] https://github.com/apache/beam-site/pull/591/
>>> [9] https://s.apache.org/beam-release-validation#gid=1082148452
>>>
>>

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

[Thomas Weise]

Hi Anton,

Thanks for working on the release.

I don't find the release blog in https://github.com/apache/beam/pull/9157 or
elsewhere?

This should be part of the release candidate [1] and I wonder why we keep
on missing it in RCs. Is there something that needs be be fixed in [1]?

The reason why I now check for this as one of the first items is that we
traditionally have done poorly communicating releases to users when this is
actually very important. The blog needs many eyes to make sure we capture
what matters in a way that makes sense to users.

Thomas






[1]
https://beam.apache.org/contribute/release-guide/#write-the-beam-blog-post-and-create-a-pull-request



On Thu, Jul 25, 2019 at 4:25 PM Rui Wang  wrote:

> Tried to verify RC1 by running Nexmark on Dataflow but found it's broken
> (at least based commands from Running+Nexmark
> ). Will
> try to debug it and rerun the process.
>
>
> -Rui
>
> On Thu, Jul 25, 2019 at 2:39 PM Anton Kedin  wrote:
>
>> Hi everyone,
>> Please review and vote on the release candidate #3 for the version
>> 2.14.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
>> 89E2FFCAE7E99CF6E6827CFEF7349F2310FFB193 [3],
>> * all artifacts to be deployed to the Maven Central Repository [4],
>> * source code tag "v2.14.0-RC1" [5], [6]
>> * website pull request listing the release [7], publishing the API
>> reference manual [8].
>> * Python artifacts are deployed along with the source release to the
>> dist.apache.org [2].
>> * Validation sheet with a tab for 2.14.0 release to help with validation
>> [9].
>>
>> The vote will be open for at least 72 hours. It is adopted by majority
>> approval, with at least 3 PMC affirmative votes.
>>
>> Thanks,
>> Anton
>>
>> [1]
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527=12345431
>> [2] https://dist.apache.org/repos/dist/dev/beam/2.14.0/
>> [3] https://dist.apache.org/repos/dist/release/beam/KEYS
>> [4]
>> https://repository.apache.org/content/repositories/orgapachebeam-1080/
>> [5] https://github.com/apache/beam/tree/v2.14.0-RC1
>> [6] https://github.com/apache/beam/tags
>> [7] https://github.com/apache/beam/pull/9157
>> [8] https://github.com/apache/beam-site/pull/591/
>> [9] https://s.apache.org/beam-release-validation#gid=1082148452
>>
>

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

[Rui Wang]

Tried to verify RC1 by running Nexmark on Dataflow but found it's broken
(at least based commands from Running+Nexmark
). Will
try to debug it and rerun the process.


-Rui

On Thu, Jul 25, 2019 at 2:39 PM Anton Kedin  wrote:

> Hi everyone,
> Please review and vote on the release candidate #3 for the version 2.14.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
> 89E2FFCAE7E99CF6E6827CFEF7349F2310FFB193 [3],
> * all artifacts to be deployed to the Maven Central Repository [4],
> * source code tag "v2.14.0-RC1" [5], [6]
> * website pull request listing the release [7], publishing the API
> reference manual [8].
> * Python artifacts are deployed along with the source release to the
> dist.apache.org [2].
> * Validation sheet with a tab for 2.14.0 release to help with validation
> [9].
>
> The vote will be open for at least 72 hours. It is adopted by majority
> approval, with at least 3 PMC affirmative votes.
>
> Thanks,
> Anton
>
> [1]
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527=12345431
> [2] https://dist.apache.org/repos/dist/dev/beam/2.14.0/
> [3] https://dist.apache.org/repos/dist/release/beam/KEYS
> [4] https://repository.apache.org/content/repositories/orgapachebeam-1080/
> [5] https://github.com/apache/beam/tree/v2.14.0-RC1
> [6] https://github.com/apache/beam/tags
> [7] https://github.com/apache/beam/pull/9157
> [8] https://github.com/apache/beam-site/pull/591/
> [9] https://s.apache.org/beam-release-validation#gid=1082148452
>

[VOTE] Release 2.14.0, release candidate #1

[Anton Kedin]

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

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

Thanks,
Anton

[1]
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527=12345431
[2] https://dist.apache.org/repos/dist/dev/beam/2.14.0/
[3] https://dist.apache.org/repos/dist/release/beam/KEYS
[4] https://repository.apache.org/content/repositories/orgapachebeam-1080/
[5] https://github.com/apache/beam/tree/v2.14.0-RC1
[6] https://github.com/apache/beam/tags
[7] https://github.com/apache/beam/pull/9157
[8] https://github.com/apache/beam-site/pull/591/
[9] https://s.apache.org/beam-release-validation#gid=1082148452