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

[Ahmet Altay]

Thank you for the comments.

Added the LICENSE and NOTICE files to the python ZIP file (also updates,
hashes and signature.) Will add this to the release guide as well. If
everyone is comfortable with this change I will proceed.

Thank you,
Ahmet

On Tue, Mar 14, 2017 at 10:38 AM, Davor Bonaci  wrote:

> +1 (binding)
>
> Contingent on adding NOTICE and LICENSE files into
> "apache-beam-0.6.0-python.zip", just as they are present in the
> "apache-beam-0.6.0-source-release.zip".
>
> On Tue, Mar 14, 2017 at 10:02 AM, Aljoscha Krettek 
> wrote:
>
> > +1 (binding)
> >
> > - verified release signature and hashes
> > - mvn install -Prelease runs smoothly
> > - created a Quickstart against the staging repo
> >   - ran Quickstart with Flink local mode
> >   - ran Quickstart against a Flink 1.2 cluster
> >
> > On Tue, Mar 14, 2017, at 01:44, Eugene Kirpichov wrote:
> > > Conclusion (see JIRA): Not a release blocker (but still a bug in
> > > TestPipeline).
> > >
> > > On Mon, Mar 13, 2017 at 5:40 PM Eugene Kirpichov  >
> > > wrote:
> > >
> > > > +Aljoscha Krettek 
> > > >
> > > > On Mon, Mar 13, 2017 at 5:30 PM Eugene Kirpichov <
> kirpic...@google.com
> > >
> > > > wrote:
> > > >
> > > > +Stas Levin  +Thomas Groh 
> > > >
> > > > On Mon, Mar 13, 2017 at 5:30 PM Eugene Kirpichov <
> kirpic...@google.com
> > >
> > > > wrote:
> > > >
> > > > https://issues.apache.org/jira/browse/BEAM-1712 might be a release
> > > > blocker.
> > > >
> > > > On Mon, Mar 13, 2017 at 4:53 PM Ahmet Altay  >
> > > > wrote:
> > > >
> > > > Thank you for all the comment so far.
> > > >
> > > > On Mon, Mar 13, 2017 at 4:23 PM, Ted Yu  wrote:
> > > >
> > > > > bq.  I would prefer that we have a .tar.gz release
> > > > >
> > > > > +1
> > > > >
> > > > > On Mon, Mar 13, 2017 at 4:21 PM, Ismaël Mejía 
> > wrote:
> > > > >
> > > > > > ​+1 (non-binding)
> > > > > >
> > > > > > - verified signatures + checksums
> > > > > > - run mvn clean install -Prelease, all artifacts build and the
> > tests
> > > > run
> > > > > > smoothly (modulo some local issues I had with the installation of
> > tox
> > > > for
> > > > > > the python sdk, I created a PR to fix those in case other people
> > can
> > > > have
> > > > > > the same trouble).
> > > > > >
> > > > > > Some remarks still to fix from the release, but that I don’t
> > consider
> > > > > > blockers:
> > > > > >
> > > > > > 1. The section Getting Started in the main README.md needs to be
> > > > updated
> > > > > > with the information about the creating/activating the
> virtualenv.
> > At
> > > > > this
> > > > > > moment just running mvn clean install won’t work without this.
> > > > >
> > > >
> > > > mvn clean install should run without any additional steps, including
> > the
> > > > creation of a virtualenv. tox will manage this process, and it is
> > already
> > > > integrated Maven.
> > > >
> > > >
> > > > > >
> > > > > > 2.  Both zip files in the current release produce a folder with
> the
> > > > same
> > > > > > name ‘apache-beam-0.6.0’. This can be messy if users unzip both
> > files
> > > > > into
> > > > > > the same folder (as happened to me, the compressed files should
> > > > produce a
> > > > > > directory with the exact same name that the file, so
> > > > > > apache-beam-0.6.0-python.zip will produce
> apache-beam-0.6.0-python
> > and
> > > > > the
> > > > > > other its respective directory.
> > > > >
> > > > >
> > > > > > 3. The name of the files of the release probably should be
> > different:
> > > > > >
> > > > > > The source release could be just apache-beam-0.6.0.zip instead of
> > > > > > apache-beam-0.6.0-source-release.zip considering that we don’t
> > have
> > > > > binary
> > > > > > artifacts, or just apache-beam-0.6.0-src.zip following the
> > convention
> > > > of
> > > > > > other apache projects.
> > > > > >
> > > > > > The python release also could be renamed from
> > > > > > apache-beam-0.6.0-bin-python.zip instead of
> > > > apache-beam-0.6.0-python.zip
> > > > > > so
> > > > > > users understand that these are executable files (but well I am
> not
> > > > sure
> > > > > > about that one considering that python is a scripting language).
> > > > >
> > > >
> > > > Python distribution is a source distribution, adding bin to the name
> > would
> > > > be confusing.
> > > >
> > > >
> > > > > >
> > > > > > Finally I would prefer that we have a .tar.gz release as JB
> > mentioned
> > > > in
> > > > > > the previous vote, and as most apache projects do. In any case if
> > the
> > > > zip
> > > > > > is somehow a requirement it would be nice to have both a .zip
> and a
> > > > > .tar.gz
> > > > > > file.
> > > > > >
> > > > >
> > > >
> > > > I think we should move this to a different thread. IMO, having a
> single
> > > > source of truth is better than having both file formats. 

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

[Davor Bonaci]

+1 (binding)

Contingent on adding NOTICE and LICENSE files into
"apache-beam-0.6.0-python.zip", just as they are present in the
"apache-beam-0.6.0-source-release.zip".

On Tue, Mar 14, 2017 at 10:02 AM, Aljoscha Krettek 
wrote:

> +1 (binding)
>
> - verified release signature and hashes
> - mvn install -Prelease runs smoothly
> - created a Quickstart against the staging repo
>   - ran Quickstart with Flink local mode
>   - ran Quickstart against a Flink 1.2 cluster
>
> On Tue, Mar 14, 2017, at 01:44, Eugene Kirpichov wrote:
> > Conclusion (see JIRA): Not a release blocker (but still a bug in
> > TestPipeline).
> >
> > On Mon, Mar 13, 2017 at 5:40 PM Eugene Kirpichov 
> > wrote:
> >
> > > +Aljoscha Krettek 
> > >
> > > On Mon, Mar 13, 2017 at 5:30 PM Eugene Kirpichov  >
> > > wrote:
> > >
> > > +Stas Levin  +Thomas Groh 
> > >
> > > On Mon, Mar 13, 2017 at 5:30 PM Eugene Kirpichov  >
> > > wrote:
> > >
> > > https://issues.apache.org/jira/browse/BEAM-1712 might be a release
> > > blocker.
> > >
> > > On Mon, Mar 13, 2017 at 4:53 PM Ahmet Altay 
> > > wrote:
> > >
> > > Thank you for all the comment so far.
> > >
> > > On Mon, Mar 13, 2017 at 4:23 PM, Ted Yu  wrote:
> > >
> > > > bq.  I would prefer that we have a .tar.gz release
> > > >
> > > > +1
> > > >
> > > > On Mon, Mar 13, 2017 at 4:21 PM, Ismaël Mejía 
> wrote:
> > > >
> > > > > ​+1 (non-binding)
> > > > >
> > > > > - verified signatures + checksums
> > > > > - run mvn clean install -Prelease, all artifacts build and the
> tests
> > > run
> > > > > smoothly (modulo some local issues I had with the installation of
> tox
> > > for
> > > > > the python sdk, I created a PR to fix those in case other people
> can
> > > have
> > > > > the same trouble).
> > > > >
> > > > > Some remarks still to fix from the release, but that I don’t
> consider
> > > > > blockers:
> > > > >
> > > > > 1. The section Getting Started in the main README.md needs to be
> > > updated
> > > > > with the information about the creating/activating the virtualenv.
> At
> > > > this
> > > > > moment just running mvn clean install won’t work without this.
> > > >
> > >
> > > mvn clean install should run without any additional steps, including
> the
> > > creation of a virtualenv. tox will manage this process, and it is
> already
> > > integrated Maven.
> > >
> > >
> > > > >
> > > > > 2.  Both zip files in the current release produce a folder with the
> > > same
> > > > > name ‘apache-beam-0.6.0’. This can be messy if users unzip both
> files
> > > > into
> > > > > the same folder (as happened to me, the compressed files should
> > > produce a
> > > > > directory with the exact same name that the file, so
> > > > > apache-beam-0.6.0-python.zip will produce apache-beam-0.6.0-python
> and
> > > > the
> > > > > other its respective directory.
> > > >
> > > >
> > > > > 3. The name of the files of the release probably should be
> different:
> > > > >
> > > > > The source release could be just apache-beam-0.6.0.zip instead of
> > > > > apache-beam-0.6.0-source-release.zip considering that we don’t
> have
> > > > binary
> > > > > artifacts, or just apache-beam-0.6.0-src.zip following the
> convention
> > > of
> > > > > other apache projects.
> > > > >
> > > > > The python release also could be renamed from
> > > > > apache-beam-0.6.0-bin-python.zip instead of
> > > apache-beam-0.6.0-python.zip
> > > > > so
> > > > > users understand that these are executable files (but well I am not
> > > sure
> > > > > about that one considering that python is a scripting language).
> > > >
> > >
> > > Python distribution is a source distribution, adding bin to the name
> would
> > > be confusing.
> > >
> > >
> > > > >
> > > > > Finally I would prefer that we have a .tar.gz release as JB
> mentioned
> > > in
> > > > > the previous vote, and as most apache projects do. In any case if
> the
> > > zip
> > > > > is somehow a requirement it would be nice to have both a .zip and a
> > > > .tar.gz
> > > > > file.
> > > > >
> > > >
> > >
> > > I think we should move this to a different thread. IMO, having a single
> > > source of truth is better than having both file formats. Between both
> file
> > > formats I don't have a strong opinion but considering the Windows
> users zip
> > > might be a portable option.
> > >
> > > Thank you,
> > > Ahmet
> > >
> > >
>

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

[Aljoscha Krettek]

+1 (binding)

- verified release signature and hashes
- mvn install -Prelease runs smoothly
- created a Quickstart against the staging repo
  - ran Quickstart with Flink local mode
  - ran Quickstart against a Flink 1.2 cluster

On Tue, Mar 14, 2017, at 01:44, Eugene Kirpichov wrote:
> Conclusion (see JIRA): Not a release blocker (but still a bug in
> TestPipeline).
> 
> On Mon, Mar 13, 2017 at 5:40 PM Eugene Kirpichov 
> wrote:
> 
> > +Aljoscha Krettek 
> >
> > On Mon, Mar 13, 2017 at 5:30 PM Eugene Kirpichov 
> > wrote:
> >
> > +Stas Levin  +Thomas Groh 
> >
> > On Mon, Mar 13, 2017 at 5:30 PM Eugene Kirpichov 
> > wrote:
> >
> > https://issues.apache.org/jira/browse/BEAM-1712 might be a release
> > blocker.
> >
> > On Mon, Mar 13, 2017 at 4:53 PM Ahmet Altay 
> > wrote:
> >
> > Thank you for all the comment so far.
> >
> > On Mon, Mar 13, 2017 at 4:23 PM, Ted Yu  wrote:
> >
> > > bq.  I would prefer that we have a .tar.gz release
> > >
> > > +1
> > >
> > > On Mon, Mar 13, 2017 at 4:21 PM, Ismaël Mejía  wrote:
> > >
> > > > ​+1 (non-binding)
> > > >
> > > > - verified signatures + checksums
> > > > - run mvn clean install -Prelease, all artifacts build and the tests
> > run
> > > > smoothly (modulo some local issues I had with the installation of tox
> > for
> > > > the python sdk, I created a PR to fix those in case other people can
> > have
> > > > the same trouble).
> > > >
> > > > Some remarks still to fix from the release, but that I don’t consider
> > > > blockers:
> > > >
> > > > 1. The section Getting Started in the main README.md needs to be
> > updated
> > > > with the information about the creating/activating the virtualenv. At
> > > this
> > > > moment just running mvn clean install won’t work without this.
> > >
> >
> > mvn clean install should run without any additional steps, including the
> > creation of a virtualenv. tox will manage this process, and it is already
> > integrated Maven.
> >
> >
> > > >
> > > > 2.  Both zip files in the current release produce a folder with the
> > same
> > > > name ‘apache-beam-0.6.0’. This can be messy if users unzip both files
> > > into
> > > > the same folder (as happened to me, the compressed files should
> > produce a
> > > > directory with the exact same name that the file, so
> > > > apache-beam-0.6.0-python.zip will produce apache-beam-0.6.0-python and
> > > the
> > > > other its respective directory.
> > >
> > >
> > > > 3. The name of the files of the release probably should be different:
> > > >
> > > > The source release could be just apache-beam-0.6.0.zip instead of
> > > > apache-beam-0.6.0-source-release.zip considering that we don’t have
> > > binary
> > > > artifacts, or just apache-beam-0.6.0-src.zip following the convention
> > of
> > > > other apache projects.
> > > >
> > > > The python release also could be renamed from
> > > > apache-beam-0.6.0-bin-python.zip instead of
> > apache-beam-0.6.0-python.zip
> > > > so
> > > > users understand that these are executable files (but well I am not
> > sure
> > > > about that one considering that python is a scripting language).
> > >
> >
> > Python distribution is a source distribution, adding bin to the name would
> > be confusing.
> >
> >
> > > >
> > > > Finally I would prefer that we have a .tar.gz release as JB mentioned
> > in
> > > > the previous vote, and as most apache projects do. In any case if the
> > zip
> > > > is somehow a requirement it would be nice to have both a .zip and a
> > > .tar.gz
> > > > file.
> > > >
> > >
> >
> > I think we should move this to a different thread. IMO, having a single
> > source of truth is better than having both file formats. Between both file
> > formats I don't have a strong opinion but considering the Windows users zip
> > might be a portable option.
> >
> > Thank you,
> > Ahmet
> >
> >

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

[Eugene Kirpichov]

Conclusion (see JIRA): Not a release blocker (but still a bug in
TestPipeline).

On Mon, Mar 13, 2017 at 5:40 PM Eugene Kirpichov 
wrote:

> +Aljoscha Krettek 
>
> On Mon, Mar 13, 2017 at 5:30 PM Eugene Kirpichov 
> wrote:
>
> +Stas Levin  +Thomas Groh 
>
> On Mon, Mar 13, 2017 at 5:30 PM Eugene Kirpichov 
> wrote:
>
> https://issues.apache.org/jira/browse/BEAM-1712 might be a release
> blocker.
>
> On Mon, Mar 13, 2017 at 4:53 PM Ahmet Altay 
> wrote:
>
> Thank you for all the comment so far.
>
> On Mon, Mar 13, 2017 at 4:23 PM, Ted Yu  wrote:
>
> > bq.  I would prefer that we have a .tar.gz release
> >
> > +1
> >
> > On Mon, Mar 13, 2017 at 4:21 PM, Ismaël Mejía  wrote:
> >
> > > ​+1 (non-binding)
> > >
> > > - verified signatures + checksums
> > > - run mvn clean install -Prelease, all artifacts build and the tests
> run
> > > smoothly (modulo some local issues I had with the installation of tox
> for
> > > the python sdk, I created a PR to fix those in case other people can
> have
> > > the same trouble).
> > >
> > > Some remarks still to fix from the release, but that I don’t consider
> > > blockers:
> > >
> > > 1. The section Getting Started in the main README.md needs to be
> updated
> > > with the information about the creating/activating the virtualenv. At
> > this
> > > moment just running mvn clean install won’t work without this.
> >
>
> mvn clean install should run without any additional steps, including the
> creation of a virtualenv. tox will manage this process, and it is already
> integrated Maven.
>
>
> > >
> > > 2.  Both zip files in the current release produce a folder with the
> same
> > > name ‘apache-beam-0.6.0’. This can be messy if users unzip both files
> > into
> > > the same folder (as happened to me, the compressed files should
> produce a
> > > directory with the exact same name that the file, so
> > > apache-beam-0.6.0-python.zip will produce apache-beam-0.6.0-python and
> > the
> > > other its respective directory.
> >
> >
> > > 3. The name of the files of the release probably should be different:
> > >
> > > The source release could be just apache-beam-0.6.0.zip instead of
> > > apache-beam-0.6.0-source-release.zip considering that we don’t have
> > binary
> > > artifacts, or just apache-beam-0.6.0-src.zip following the convention
> of
> > > other apache projects.
> > >
> > > The python release also could be renamed from
> > > apache-beam-0.6.0-bin-python.zip instead of
> apache-beam-0.6.0-python.zip
> > > so
> > > users understand that these are executable files (but well I am not
> sure
> > > about that one considering that python is a scripting language).
> >
>
> Python distribution is a source distribution, adding bin to the name would
> be confusing.
>
>
> > >
> > > Finally I would prefer that we have a .tar.gz release as JB mentioned
> in
> > > the previous vote, and as most apache projects do. In any case if the
> zip
> > > is somehow a requirement it would be nice to have both a .zip and a
> > .tar.gz
> > > file.
> > >
> >
>
> I think we should move this to a different thread. IMO, having a single
> source of truth is better than having both file formats. Between both file
> formats I don't have a strong opinion but considering the Windows users zip
> might be a portable option.
>
> Thank you,
> Ahmet
>
>

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

[Eugene Kirpichov]

+Aljoscha Krettek 

On Mon, Mar 13, 2017 at 5:30 PM Eugene Kirpichov 
wrote:

> +Stas Levin  +Thomas Groh 
>
> On Mon, Mar 13, 2017 at 5:30 PM Eugene Kirpichov 
> wrote:
>
> https://issues.apache.org/jira/browse/BEAM-1712 might be a release
> blocker.
>
> On Mon, Mar 13, 2017 at 4:53 PM Ahmet Altay 
> wrote:
>
> Thank you for all the comment so far.
>
> On Mon, Mar 13, 2017 at 4:23 PM, Ted Yu  wrote:
>
> > bq.  I would prefer that we have a .tar.gz release
> >
> > +1
> >
> > On Mon, Mar 13, 2017 at 4:21 PM, Ismaël Mejía  wrote:
> >
> > > ​+1 (non-binding)
> > >
> > > - verified signatures + checksums
> > > - run mvn clean install -Prelease, all artifacts build and the tests
> run
> > > smoothly (modulo some local issues I had with the installation of tox
> for
> > > the python sdk, I created a PR to fix those in case other people can
> have
> > > the same trouble).
> > >
> > > Some remarks still to fix from the release, but that I don’t consider
> > > blockers:
> > >
> > > 1. The section Getting Started in the main README.md needs to be
> updated
> > > with the information about the creating/activating the virtualenv. At
> > this
> > > moment just running mvn clean install won’t work without this.
> >
>
> mvn clean install should run without any additional steps, including the
> creation of a virtualenv. tox will manage this process, and it is already
> integrated Maven.
>
>
> > >
> > > 2.  Both zip files in the current release produce a folder with the
> same
> > > name ‘apache-beam-0.6.0’. This can be messy if users unzip both files
> > into
> > > the same folder (as happened to me, the compressed files should
> produce a
> > > directory with the exact same name that the file, so
> > > apache-beam-0.6.0-python.zip will produce apache-beam-0.6.0-python and
> > the
> > > other its respective directory.
> >
> >
> > > 3. The name of the files of the release probably should be different:
> > >
> > > The source release could be just apache-beam-0.6.0.zip instead of
> > > apache-beam-0.6.0-source-release.zip considering that we don’t have
> > binary
> > > artifacts, or just apache-beam-0.6.0-src.zip following the convention
> of
> > > other apache projects.
> > >
> > > The python release also could be renamed from
> > > apache-beam-0.6.0-bin-python.zip instead of
> apache-beam-0.6.0-python.zip
> > > so
> > > users understand that these are executable files (but well I am not
> sure
> > > about that one considering that python is a scripting language).
> >
>
> Python distribution is a source distribution, adding bin to the name would
> be confusing.
>
>
> > >
> > > Finally I would prefer that we have a .tar.gz release as JB mentioned
> in
> > > the previous vote, and as most apache projects do. In any case if the
> zip
> > > is somehow a requirement it would be nice to have both a .zip and a
> > .tar.gz
> > > file.
> > >
> >
>
> I think we should move this to a different thread. IMO, having a single
> source of truth is better than having both file formats. Between both file
> formats I don't have a strong opinion but considering the Windows users zip
> might be a portable option.
>
> Thank you,
> Ahmet
>
>

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

[Eugene Kirpichov]

+Stas Levin  +Thomas Groh 

On Mon, Mar 13, 2017 at 5:30 PM Eugene Kirpichov 
wrote:

> https://issues.apache.org/jira/browse/BEAM-1712 might be a release
> blocker.
>
> On Mon, Mar 13, 2017 at 4:53 PM Ahmet Altay 
> wrote:
>
> Thank you for all the comment so far.
>
> On Mon, Mar 13, 2017 at 4:23 PM, Ted Yu  wrote:
>
> > bq.  I would prefer that we have a .tar.gz release
> >
> > +1
> >
> > On Mon, Mar 13, 2017 at 4:21 PM, Ismaël Mejía  wrote:
> >
> > > ​+1 (non-binding)
> > >
> > > - verified signatures + checksums
> > > - run mvn clean install -Prelease, all artifacts build and the tests
> run
> > > smoothly (modulo some local issues I had with the installation of tox
> for
> > > the python sdk, I created a PR to fix those in case other people can
> have
> > > the same trouble).
> > >
> > > Some remarks still to fix from the release, but that I don’t consider
> > > blockers:
> > >
> > > 1. The section Getting Started in the main README.md needs to be
> updated
> > > with the information about the creating/activating the virtualenv. At
> > this
> > > moment just running mvn clean install won’t work without this.
> >
>
> mvn clean install should run without any additional steps, including the
> creation of a virtualenv. tox will manage this process, and it is already
> integrated Maven.
>
>
> > >
> > > 2.  Both zip files in the current release produce a folder with the
> same
> > > name ‘apache-beam-0.6.0’. This can be messy if users unzip both files
> > into
> > > the same folder (as happened to me, the compressed files should
> produce a
> > > directory with the exact same name that the file, so
> > > apache-beam-0.6.0-python.zip will produce apache-beam-0.6.0-python and
> > the
> > > other its respective directory.
> >
> >
> > > 3. The name of the files of the release probably should be different:
> > >
> > > The source release could be just apache-beam-0.6.0.zip instead of
> > > apache-beam-0.6.0-source-release.zip considering that we don’t have
> > binary
> > > artifacts, or just apache-beam-0.6.0-src.zip following the convention
> of
> > > other apache projects.
> > >
> > > The python release also could be renamed from
> > > apache-beam-0.6.0-bin-python.zip instead of
> apache-beam-0.6.0-python.zip
> > > so
> > > users understand that these are executable files (but well I am not
> sure
> > > about that one considering that python is a scripting language).
> >
>
> Python distribution is a source distribution, adding bin to the name would
> be confusing.
>
>
> > >
> > > Finally I would prefer that we have a .tar.gz release as JB mentioned
> in
> > > the previous vote, and as most apache projects do. In any case if the
> zip
> > > is somehow a requirement it would be nice to have both a .zip and a
> > .tar.gz
> > > file.
> > >
> >
>
> I think we should move this to a different thread. IMO, having a single
> source of truth is better than having both file formats. Between both file
> formats I don't have a strong opinion but considering the Windows users zip
> might be a portable option.
>
> Thank you,
> Ahmet
>
>

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

[Eugene Kirpichov]

https://issues.apache.org/jira/browse/BEAM-1712 might be a release blocker.

On Mon, Mar 13, 2017 at 4:53 PM Ahmet Altay 
wrote:

> Thank you for all the comment so far.
>
> On Mon, Mar 13, 2017 at 4:23 PM, Ted Yu  wrote:
>
> > bq.  I would prefer that we have a .tar.gz release
> >
> > +1
> >
> > On Mon, Mar 13, 2017 at 4:21 PM, Ismaël Mejía  wrote:
> >
> > > ​+1 (non-binding)
> > >
> > > - verified signatures + checksums
> > > - run mvn clean install -Prelease, all artifacts build and the tests
> run
> > > smoothly (modulo some local issues I had with the installation of tox
> for
> > > the python sdk, I created a PR to fix those in case other people can
> have
> > > the same trouble).
> > >
> > > Some remarks still to fix from the release, but that I don’t consider
> > > blockers:
> > >
> > > 1. The section Getting Started in the main README.md needs to be
> updated
> > > with the information about the creating/activating the virtualenv. At
> > this
> > > moment just running mvn clean install won’t work without this.
> >
>
> mvn clean install should run without any additional steps, including the
> creation of a virtualenv. tox will manage this process, and it is already
> integrated Maven.
>
>
> > >
> > > 2.  Both zip files in the current release produce a folder with the
> same
> > > name ‘apache-beam-0.6.0’. This can be messy if users unzip both files
> > into
> > > the same folder (as happened to me, the compressed files should
> produce a
> > > directory with the exact same name that the file, so
> > > apache-beam-0.6.0-python.zip will produce apache-beam-0.6.0-python and
> > the
> > > other its respective directory.
> >
> >
> > > 3. The name of the files of the release probably should be different:
> > >
> > > The source release could be just apache-beam-0.6.0.zip instead of
> > > apache-beam-0.6.0-source-release.zip considering that we don’t have
> > binary
> > > artifacts, or just apache-beam-0.6.0-src.zip following the convention
> of
> > > other apache projects.
> > >
> > > The python release also could be renamed from
> > > apache-beam-0.6.0-bin-python.zip instead of
> apache-beam-0.6.0-python.zip
> > > so
> > > users understand that these are executable files (but well I am not
> sure
> > > about that one considering that python is a scripting language).
> >
>
> Python distribution is a source distribution, adding bin to the name would
> be confusing.
>
>
> > >
> > > Finally I would prefer that we have a .tar.gz release as JB mentioned
> in
> > > the previous vote, and as most apache projects do. In any case if the
> zip
> > > is somehow a requirement it would be nice to have both a .zip and a
> > .tar.gz
> > > file.
> > >
> >
>
> I think we should move this to a different thread. IMO, having a single
> source of truth is better than having both file formats. Between both file
> formats I don't have a strong opinion but considering the Windows users zip
> might be a portable option.
>
> Thank you,
> Ahmet
>

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

[Ted Yu]

bq.  I would prefer that we have a .tar.gz release

+1

On Mon, Mar 13, 2017 at 4:21 PM, Ismaël Mejía  wrote:

> ​+1 (non-binding)
>
> - verified signatures + checksums
> - run mvn clean install -Prelease, all artifacts build and the tests run
> smoothly (modulo some local issues I had with the installation of tox for
> the python sdk, I created a PR to fix those in case other people can have
> the same trouble).
>
> Some remarks still to fix from the release, but that I don’t consider
> blockers:
>
> 1. The section Getting Started in the main README.md needs to be updated
> with the information about the creating/activating the virtualenv. At this
> moment just running mvn clean install won’t work without this.
>
> 2.  Both zip files in the current release produce a folder with the same
> name ‘apache-beam-0.6.0’. This can be messy if users unzip both files into
> the same folder (as happened to me, the compressed files should produce a
> directory with the exact same name that the file, so
> apache-beam-0.6.0-python.zip will produce apache-beam-0.6.0-python and the
> other its respective directory.
>
> 3. The name of the files of the release probably should be different:
>
> The source release could be just apache-beam-0.6.0.zip instead of
> apache-beam-0.6.0-source-release.zip considering that we don’t have binary
> artifacts, or just apache-beam-0.6.0-src.zip following the convention of
> other apache projects.
>
> The python release also could be renamed from
> apache-beam-0.6.0-bin-python.zip instead of apache-beam-0.6.0-python.zip
> so
> users understand that these are executable files (but well I am not sure
> about that one considering that python is a scripting language).
>
> Finally I would prefer that we have a .tar.gz release as JB mentioned in
> the previous vote, and as most apache projects do. In any case if the zip
> is somehow a requirement it would be nice to have both a .zip and a .tar.gz
> file.
>

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

[Ismaël Mejía]

​+1 (non-binding)

- verified signatures + checksums
- run mvn clean install -Prelease, all artifacts build and the tests run
smoothly (modulo some local issues I had with the installation of tox for
the python sdk, I created a PR to fix those in case other people can have
the same trouble).

Some remarks still to fix from the release, but that I don’t consider
blockers:

1. The section Getting Started in the main README.md needs to be updated
with the information about the creating/activating the virtualenv. At this
moment just running mvn clean install won’t work without this.

2.  Both zip files in the current release produce a folder with the same
name ‘apache-beam-0.6.0’. This can be messy if users unzip both files into
the same folder (as happened to me, the compressed files should produce a
directory with the exact same name that the file, so
apache-beam-0.6.0-python.zip will produce apache-beam-0.6.0-python and the
other its respective directory.

3. The name of the files of the release probably should be different:

The source release could be just apache-beam-0.6.0.zip instead of
apache-beam-0.6.0-source-release.zip considering that we don’t have binary
artifacts, or just apache-beam-0.6.0-src.zip following the convention of
other apache projects.

The python release also could be renamed from
apache-beam-0.6.0-bin-python.zip instead of apache-beam-0.6.0-python.zip so
users understand that these are executable files (but well I am not sure
about that one considering that python is a scripting language).

Finally I would prefer that we have a .tar.gz release as JB mentioned in
the previous vote, and as most apache projects do. In any case if the zip
is somehow a requirement it would be nice to have both a .zip and a .tar.gz
file.

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

[Robert Bradshaw]

+1 (binding)

On Mon, Mar 13, 2017 at 11:10 AM, Robert Bradshaw 
wrote:

> On Sat, Mar 11, 2017 at 11:19 PM, Ahmet Altay 
> wrote:
>
>> On Sat, Mar 11, 2017 at 11:48 AM, Robert Bradshaw <
>> rober...@google.com.invalid> wrote:
>>
>> > On Fri, Mar 10, 2017 at 9:05 PM, Ahmet Altay 
>> > wrote:
>> >
>> > > Hi everyone,
>> > >
>> > > Please review and vote on the release candidate #2 for the version
>> 0.6.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 6096FA00 [3],
>> > > * all artifacts to be deployed to the Maven Central Repository [4],
>> > > * source code tag "v0.6.0-RC2" [5],
>> > > * website pull request listing the release and publishing the API
>> > reference
>> > > manual [6].
>> > > * python artifacts are deployed along with the source release to to
>> > > dist.apache.org [2].
>> > >
>> >
>> > Are there plans also to deploy this at PyPi, and if so, what are the
>> > details?
>> >
>>
>> Yes, I think we should publish on PyPI. It will make the package usefeul
>> to
>> many Python developers.
>>
>> My recommendation for details:
>> * PyPI requires one time registeration of the package. The most important
>> decision here is the package name. Our current package name apache_beam is
>> available. (Unless we decide to change this, there is no need to make a
>> change to this RC2.)
>>
>
> That name makes sense to me. Any objections? Do we need a separate vote,
> or should we just wait until this one passes.
>
>
>> * PyPI packages support two roles Owner and Maintainer. A Maintainer can
>> deploy new releases. A Owner (in addition to Maintainer permissions), can
>> manage the package and add/remove Maintainers/Owners. (This is my best
>> understanding, documentation is sparse [1].) I suggest that a PMC member
>> registers the package and become an owner. After that PMC can decide to
>> add
>> more owners and maintainers. (Release manager needs to be at least a
>> maintainer.)
>>
>
> I'll be happy to do this.
>
>
>> * One-line change to release guide to use a command line tool to upload
>> approved release to PyPI.
>
> Note that there is no need to rebuild the RC2 to execute the above
>> proposal.
>>
>> Thank you,
>> Ahmet
>>
>> [1] https://docs.python.org/2/distutils/packageindex.html#pypi-overview
>>
>>
>> >
>> >
>> > > A suite of Jenkins jobs:
>> > > * PreCommit_Java_MavenInstall [7],
>> > > * PostCommit_Java_MavenInstall [8],
>> > > * PostCommit_Java_RunnableOnService_Apex [9],
>> > > * PostCommit_Java_RunnableOnService_Flink [10],
>> > > * PostCommit_Java_RunnableOnService_Spark [11],
>> > > * PostCommit_Java_RunnableOnService_Dataflow [12]
>> > > * PostCommit_Python_Verify [13]
>> > >
>> > > Compared to release candidate #1, this candidate contains pull
>> requests
>> > > #2217 [14], #2221 [15], # [16], #2224 [17], and #2225 [18]; see
>> the
>> > > discussion for reasoning.
>>
>
> I verified the Python package installs fine in a clean virtualenv. The
> hashes look good too now. However, when running wordcount_minimal I get
>
>   File "/usr/local/google/home/robertwb/scratch/beam-0.6.0-test/
> local/lib/python2.7/site-packages/apache_beam/io/fileio.py", line 281, in
> glob
> return gcsio.GcsIO().glob(path, limit)
> AttributeError: 'NoneType' object has no attribute 'GcsIO'
>
> It would be good to have a better error when gcp is not installed (the
> default). Not sure if this should block the release, but should be an easy
> fix (I'll create a PR).
>

https://github.com/apache/beam/pull/2233 (maybe shouldn't hold up this
pre-stable release).


> However, even after installing gcp I get
>
> Traceback (most recent call last):
>   File "wordcount_minimal.py", line 123, in 
> run()
>   File "wordcount_minimal.py", line 118, in run
> p.run().wait_until_finish()
>   File "/usr/local/google/home/robertwb/scratch/beam-0.6.0-test/
> local/lib/python2.7/site-packages/apache_beam/pipeline.py", line 163, in
> run
> return self.runner.run(self)
>   File "/usr/local/google/home/robertwb/scratch/beam-0.6.0-test/
> local/lib/python2.7/site-packages/apache_beam/runners/dataflow/dataflow_runner.py",
> line 175, in run
> self.dataflow_client.create_job(self.job), self)
>   File "/usr/local/google/home/robertwb/scratch/beam-0.6.0-test/
> local/lib/python2.7/site-packages/apache_beam/utils/retry.py", line 174,
> in wrapper
> return fun(*args, **kwargs)
>   File "/usr/local/google/home/robertwb/scratch/beam-0.6.0-test/
> local/lib/python2.7/site-packages/apache_beam/runners/dataflow/internal/apiclient.py",
> line 411, in create_job
> self.create_job_description(job)

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

[Robert Bradshaw]

On Sat, Mar 11, 2017 at 11:19 PM, Ahmet Altay 
wrote:

> On Sat, Mar 11, 2017 at 11:48 AM, Robert Bradshaw <
> rober...@google.com.invalid> wrote:
>
> > On Fri, Mar 10, 2017 at 9:05 PM, Ahmet Altay 
> > wrote:
> >
> > > Hi everyone,
> > >
> > > Please review and vote on the release candidate #2 for the version
> 0.6.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 6096FA00 [3],
> > > * all artifacts to be deployed to the Maven Central Repository [4],
> > > * source code tag "v0.6.0-RC2" [5],
> > > * website pull request listing the release and publishing the API
> > reference
> > > manual [6].
> > > * python artifacts are deployed along with the source release to to
> > > dist.apache.org [2].
> > >
> >
> > Are there plans also to deploy this at PyPi, and if so, what are the
> > details?
> >
>
> Yes, I think we should publish on PyPI. It will make the package usefeul to
> many Python developers.
>
> My recommendation for details:
> * PyPI requires one time registeration of the package. The most important
> decision here is the package name. Our current package name apache_beam is
> available. (Unless we decide to change this, there is no need to make a
> change to this RC2.)
>

That name makes sense to me. Any objections? Do we need a separate vote, or
should we just wait until this one passes.


> * PyPI packages support two roles Owner and Maintainer. A Maintainer can
> deploy new releases. A Owner (in addition to Maintainer permissions), can
> manage the package and add/remove Maintainers/Owners. (This is my best
> understanding, documentation is sparse [1].) I suggest that a PMC member
> registers the package and become an owner. After that PMC can decide to add
> more owners and maintainers. (Release manager needs to be at least a
> maintainer.)
>

I'll be happy to do this.


> * One-line change to release guide to use a command line tool to upload
> approved release to PyPI.

Note that there is no need to rebuild the RC2 to execute the above proposal.
>
> Thank you,
> Ahmet
>
> [1] https://docs.python.org/2/distutils/packageindex.html#pypi-overview
>
>
> >
> >
> > > A suite of Jenkins jobs:
> > > * PreCommit_Java_MavenInstall [7],
> > > * PostCommit_Java_MavenInstall [8],
> > > * PostCommit_Java_RunnableOnService_Apex [9],
> > > * PostCommit_Java_RunnableOnService_Flink [10],
> > > * PostCommit_Java_RunnableOnService_Spark [11],
> > > * PostCommit_Java_RunnableOnService_Dataflow [12]
> > > * PostCommit_Python_Verify [13]
> > >
> > > Compared to release candidate #1, this candidate contains pull requests
> > > #2217 [14], #2221 [15], # [16], #2224 [17], and #2225 [18]; see the
> > > discussion for reasoning.
>

I verified the Python package installs fine in a clean virtualenv. The
hashes look good too now. However, when running wordcount_minimal I get

  File
"/usr/local/google/home/robertwb/scratch/beam-0.6.0-test/local/lib/python2.7/site-packages/apache_beam/io/fileio.py",
line 281, in glob
return gcsio.GcsIO().glob(path, limit)
AttributeError: 'NoneType' object has no attribute 'GcsIO'

It would be good to have a better error when gcp is not installed (the
default). Not sure if this should block the release, but should be an easy
fix (I'll create a PR). However, even after installing gcp I get

Traceback (most recent call last):
  File "wordcount_minimal.py", line 123, in 
run()
  File "wordcount_minimal.py", line 118, in run
p.run().wait_until_finish()
  File
"/usr/local/google/home/robertwb/scratch/beam-0.6.0-test/local/lib/python2.7/site-packages/apache_beam/pipeline.py",
line 163, in run
return self.runner.run(self)
  File
"/usr/local/google/home/robertwb/scratch/beam-0.6.0-test/local/lib/python2.7/site-packages/apache_beam/runners/dataflow/dataflow_runner.py",
line 175, in run
self.dataflow_client.create_job(self.job), self)
  File
"/usr/local/google/home/robertwb/scratch/beam-0.6.0-test/local/lib/python2.7/site-packages/apache_beam/utils/retry.py",
line 174, in wrapper
return fun(*args, **kwargs)
  File
"/usr/local/google/home/robertwb/scratch/beam-0.6.0-test/local/lib/python2.7/site-packages/apache_beam/runners/dataflow/internal/apiclient.py",
line 411, in create_job
self.create_job_description(job)
  File
"/usr/local/google/home/robertwb/scratch/beam-0.6.0-test/local/lib/python2.7/site-packages/apache_beam/runners/dataflow/internal/apiclient.py",
line 432, in create_job_description
job.options, file_copy=self._gcs_file_copy)
  File

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

[Jean-Baptiste Onofré]

+1 (binding)

- Build is OK on the tag
- Checked the signature (updated)
- Checked checksums
- Checked ASF headers
- Run tests on my samples (Java SDK)

Regards
JB

On 03/11/2017 06:05 AM, Ahmet Altay wrote:

Hi everyone,

Please review and vote on the release candidate #2 for the version 0.6.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 6096FA00 [3],
* all artifacts to be deployed to the Maven Central Repository [4],
* source code tag "v0.6.0-RC2" [5],
* website pull request listing the release and publishing the API reference
manual [6].
* python artifacts are deployed along with the source release to to
dist.apache.org [2].

A suite of Jenkins jobs:
* PreCommit_Java_MavenInstall [7],
* PostCommit_Java_MavenInstall [8],
* PostCommit_Java_RunnableOnService_Apex [9],
* PostCommit_Java_RunnableOnService_Flink [10],
* PostCommit_Java_RunnableOnService_Spark [11],
* PostCommit_Java_RunnableOnService_Dataflow [12]
* PostCommit_Python_Verify [13]

Compared to release candidate #1, this candidate contains pull requests
#2217 [14], #2221 [15], # [16], #2224 [17], and #2225 [18]; see the
discussion for reasoning.

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?proje
ctId=12319527=12339256
[2] https://dist.apache.org/repos/dist/dev/beam/0.6.0/
[3] https://dist.apache.org/repos/dist/dev/beam/KEYS
[4] https://repository.apache.org/content/repositories/orgapachebeam-1013/
[5] https://git-wip-us.apache.org/repos/asf?p=beam.git;a=tag;h=r
efs/tags/v0.6.0-RC2
[6] https://github.com/apache/beam-site/pull/175
[7] https://builds.apache.org/view/Beam/job/beam_PreCommit_Java_
MavenInstall/8340/
[8] https://builds.apache.org/view/Beam/job/beam_PostCommit_
Java_MavenInstall/2877/
[9] https://builds.apache.org/view/Beam/job/beam_PostCommit_Java
_RunnableOnService_Apex/736/
[10] https://builds.apache.org/view/Beam/job/beam_PostCommit_Java
_RunnableOnService_Flink/1895/
[11] https://builds.apache.org/view/Beam/job/beam_PostCommit_Java
_RunnableOnService_Spark/1207/
[12] https://builds.apache.org/view/Beam/job/beam_PostCommit_Java_
RunnableOnService_Dataflow/2526/
[13] https://builds.apache.org/view/Beam/job/beam_PostCommit_Pyth
on_Verify/1481/
[14] https://github.com/apache/beam/pull/2217
[15] https://github.com/apache/beam/pull/2221
[16] https://github.com/apache/beam/pull/
[17] https://github.com/apache/beam/pull/2224
[18] https://github.com/apache/beam/pull/2225



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

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

[Ahmet Altay]

Ismaël,

It is my mistake, I hashed files before the rename. I fixed the two files:

apache-beam-0.6.0-python.zip.md5
apache-beam-0.6.0-python.zip.sha1

Note that, there are no changes to the calculated hashes or to the zip file
itself.

I will document the correct procedure in my update to release guide after
this release.

Ahmet


On Sun, Mar 12, 2017 at 10:40 AM, Tibor Kiss  wrote:

> +1
>
> Details:
>  - Built locally with 'mvn clean install –Prelease'
>  - Needed to change pip2 to pip2.7. This issue is known on OS X and shall
> not block the release in my opinion.
>  - Sanity check on Python-SDK:
>  - apache-beam-0.6.0.tar.gz has the same content as
> apache-beam-0.6.0.zip
>  - ran wordcount, estimate_pi examples
>  - Checked code from getting started guide. The document is not 100%
> accurate, but that shall not hold up the release.
>
> Thanks for putting this RC together!
>
> - Tibor
>
> On 3/11/17, 6:05 AM, "Ahmet Altay"  wrote:
>
> Hi everyone,
>
> Please review and vote on the release candidate #2 for the version
> 0.6.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 6096FA00 [3],
> * all artifacts to be deployed to the Maven Central Repository [4],
> * source code tag "v0.6.0-RC2" [5],
> * website pull request listing the release and publishing the API
> reference
> manual [6].
> * python artifacts are deployed along with the source release to to
> dist.apache.org [2].
>
> A suite of Jenkins jobs:
> * PreCommit_Java_MavenInstall [7],
> * PostCommit_Java_MavenInstall [8],
> * PostCommit_Java_RunnableOnService_Apex [9],
> * PostCommit_Java_RunnableOnService_Flink [10],
> * PostCommit_Java_RunnableOnService_Spark [11],
> * PostCommit_Java_RunnableOnService_Dataflow [12]
> * PostCommit_Python_Verify [13]
>
> Compared to release candidate #1, this candidate contains pull requests
> #2217 [14], #2221 [15], # [16], #2224 [17], and #2225 [18]; see the
> discussion for reasoning.
>
> 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?proje
> ctId=12319527=12339256
> [2] https://dist.apache.org/repos/dist/dev/beam/0.6.0/
> [3] https://dist.apache.org/repos/dist/dev/beam/KEYS
> [4] https://repository.apache.org/content/repositories/
> orgapachebeam-1013/
> [5] https://git-wip-us.apache.org/repos/asf?p=beam.git;a=tag;h=r
> efs/tags/v0.6.0-RC2
> [6] https://github.com/apache/beam-site/pull/175
> [7] https://builds.apache.org/view/Beam/job/beam_PreCommit_Java_
> MavenInstall/8340/
> [8] https://builds.apache.org/view/Beam/job/beam_PostCommit_
> Java_MavenInstall/2877/
> [9] https://builds.apache.org/view/Beam/job/beam_PostCommit_Java
> _RunnableOnService_Apex/736/
> [10] https://builds.apache.org/view/Beam/job/beam_PostCommit_Java
> _RunnableOnService_Flink/1895/
> [11] https://builds.apache.org/view/Beam/job/beam_PostCommit_Java
> _RunnableOnService_Spark/1207/
> [12] https://builds.apache.org/view/Beam/job/beam_PostCommit_Java_
> RunnableOnService_Dataflow/2526/
> [13] https://builds.apache.org/view/Beam/job/beam_PostCommit_Pyth
> on_Verify/1481/
> [14] https://github.com/apache/beam/pull/2217
> [15] https://github.com/apache/beam/pull/2221
> [16] https://github.com/apache/beam/pull/
> [17] https://github.com/apache/beam/pull/2224
> [18] https://github.com/apache/beam/pull/2225
>
>
>

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

[Tibor Kiss]

+1

Details:
 - Built locally with 'mvn clean install –Prelease'
 - Needed to change pip2 to pip2.7. This issue is known on OS X and shall not 
block the release in my opinion.
 - Sanity check on Python-SDK:
 - apache-beam-0.6.0.tar.gz has the same content as apache-beam-0.6.0.zip
 - ran wordcount, estimate_pi examples
 - Checked code from getting started guide. The document is not 100% 
accurate, but that shall not hold up the release.

Thanks for putting this RC together!

- Tibor

On 3/11/17, 6:05 AM, "Ahmet Altay"  wrote:

Hi everyone,

Please review and vote on the release candidate #2 for the version 0.6.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 6096FA00 [3],
* all artifacts to be deployed to the Maven Central Repository [4],
* source code tag "v0.6.0-RC2" [5],
* website pull request listing the release and publishing the API reference
manual [6].
* python artifacts are deployed along with the source release to to
dist.apache.org [2].

A suite of Jenkins jobs:
* PreCommit_Java_MavenInstall [7],
* PostCommit_Java_MavenInstall [8],
* PostCommit_Java_RunnableOnService_Apex [9],
* PostCommit_Java_RunnableOnService_Flink [10],
* PostCommit_Java_RunnableOnService_Spark [11],
* PostCommit_Java_RunnableOnService_Dataflow [12]
* PostCommit_Python_Verify [13]

Compared to release candidate #1, this candidate contains pull requests
#2217 [14], #2221 [15], # [16], #2224 [17], and #2225 [18]; see the
discussion for reasoning.

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?proje
ctId=12319527=12339256
[2] https://dist.apache.org/repos/dist/dev/beam/0.6.0/
[3] https://dist.apache.org/repos/dist/dev/beam/KEYS
[4] https://repository.apache.org/content/repositories/orgapachebeam-1013/
[5] https://git-wip-us.apache.org/repos/asf?p=beam.git;a=tag;h=r
efs/tags/v0.6.0-RC2
[6] https://github.com/apache/beam-site/pull/175
[7] https://builds.apache.org/view/Beam/job/beam_PreCommit_Java_
MavenInstall/8340/
[8] https://builds.apache.org/view/Beam/job/beam_PostCommit_
Java_MavenInstall/2877/
[9] https://builds.apache.org/view/Beam/job/beam_PostCommit_Java
_RunnableOnService_Apex/736/
[10] https://builds.apache.org/view/Beam/job/beam_PostCommit_Java
_RunnableOnService_Flink/1895/
[11] https://builds.apache.org/view/Beam/job/beam_PostCommit_Java
_RunnableOnService_Spark/1207/
[12] https://builds.apache.org/view/Beam/job/beam_PostCommit_Java_
RunnableOnService_Dataflow/2526/
[13] https://builds.apache.org/view/Beam/job/beam_PostCommit_Pyth
on_Verify/1481/
[14] https://github.com/apache/beam/pull/2217
[15] https://github.com/apache/beam/pull/2221
[16] https://github.com/apache/beam/pull/
[17] https://github.com/apache/beam/pull/2224
[18] https://github.com/apache/beam/pull/2225

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

[Ted Yu]

I was able to run "mvn clean install -Prelease" command successfully, too.

On Sun, Mar 12, 2017 at 12:02 AM, Ahmet Altay 
wrote:

> Amit,
>
> I was able to successfully build in a clean environment with the following
> commands:
>
> git checkout tags/v0.6.0-RC2 -b RC2
> mvn clean install -Prelease
>
> I am not a very familiar with maven build process, it would be great if
> someone else can also confirm this.
>
> Ahmet
>
>
>
> On Sat, Mar 11, 2017 at 11:00 PM, Amit Sela  wrote:
>
> > Building the RC2 tag failed for me with: "mvn clean install -Prelease"
> on a
> > missing artifact "beam-sdks-java-harness" when trying to build
> > "beam-sdks-java-javadoc".
> >
> > I want to make sure It's not something local that happens in my env. so
> if
> > anyone else could validate this it would be great.
> >
> > Amit
> >
> > On Sat, Mar 11, 2017 at 9:48 PM Robert Bradshaw
> > 
> > wrote:
> >
> > > On Fri, Mar 10, 2017 at 9:05 PM, Ahmet Altay  >
> > > wrote:
> > >
> > > > Hi everyone,
> > > >
> > > > Please review and vote on the release candidate #2 for the version
> > 0.6.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 6096FA00 [3],
> > > > * all artifacts to be deployed to the Maven Central Repository [4],
> > > > * source code tag "v0.6.0-RC2" [5],
> > > > * website pull request listing the release and publishing the API
> > > reference
> > > > manual [6].
> > > > * python artifacts are deployed along with the source release to to
> > > > dist.apache.org [2].
> > > >
> > >
> > > Are there plans also to deploy this at PyPi, and if so, what are the
> > > details?
> > >
> > >
> > > > A suite of Jenkins jobs:
> > > > * PreCommit_Java_MavenInstall [7],
> > > > * PostCommit_Java_MavenInstall [8],
> > > > * PostCommit_Java_RunnableOnService_Apex [9],
> > > > * PostCommit_Java_RunnableOnService_Flink [10],
> > > > * PostCommit_Java_RunnableOnService_Spark [11],
> > > > * PostCommit_Java_RunnableOnService_Dataflow [12]
> > > > * PostCommit_Python_Verify [13]
> > > >
> > > > Compared to release candidate #1, this candidate contains pull
> requests
> > > > #2217 [14], #2221 [15], # [16], #2224 [17], and #2225 [18]; see
> the
> > > > discussion for reasoning.
> > > >
> > > > 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?proje
> > > > ctId=12319527=12339256
> > > > [2] https://dist.apache.org/repos/dist/dev/beam/0.6.0/
> > > > [3] https://dist.apache.org/repos/dist/dev/beam/KEYS
> > > > [4]
> > > https://repository.apache.org/content/repositories/orgapachebeam-1013/
> > > > [5] https://git-wip-us.apache.org/repos/asf?p=beam.git;a=tag;h=r
> > > > efs/tags/v0.6.0-RC2
> > > > [6] https://github.com/apache/beam-site/pull/175
> > > > [7] https://builds.apache.org/view/Beam/job/beam_PreCommit_Java_
> > > > MavenInstall/8340/
> > > > [8] https://builds.apache.org/view/Beam/job/beam_PostCommit_
> > > > Java_MavenInstall/2877/
> > > > [9] https://builds.apache.org/view/Beam/job/beam_PostCommit_Java
> > > > _RunnableOnService_Apex/736/
> > > > [10] https://builds.apache.org/view/Beam/job/beam_PostCommit_Java
> > > > _RunnableOnService_Flink/1895/
> > > > [11] https://builds.apache.org/view/Beam/job/beam_PostCommit_Java
> > > > _RunnableOnService_Spark/1207/
> > > > [12] https://builds.apache.org/view/Beam/job/beam_PostCommit_Java_
> > > > RunnableOnService_Dataflow/2526/
> > > > [13] https://builds.apache.org/view/Beam/job/beam_PostCommit_Pyth
> > > > on_Verify/1481/
> > > > [14] https://github.com/apache/beam/pull/2217
> > > > [15] https://github.com/apache/beam/pull/2221
> > > > [16] https://github.com/apache/beam/pull/
> > > > [17] https://github.com/apache/beam/pull/2224
> > > > [18] https://github.com/apache/beam/pull/2225
> > > >
> > >
> >
>

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

[Ismaël Mejía]

I found an issue too with the .md5 and sha1 files of the python release,
they refer to a different default file (a forgotten part of the renaming):

curl
https://dist.apache.org/repos/dist/dev/beam/0.6.0/apache-beam-0.6.0-python.zip.md5
7d4170e381ce0e1aa8d11bee2e63d151  apache-beam-0.6.0.zip

This one shuld have been apache-beam-0.6.0-python.zip and the same for the
sha1 because if users run the classic tools to validate:
md5sum -c apache-beam-0.6.0-python.zip.md5
md5sum: apache-beam-0.6.0.zip: No such file or directory
apache-beam-0.6.0.zip: FAILED open or read
md5sum: WARNING: 1 listed file could not be read

I don't know if this is critical to trigger another vote, but it is an
issue too.
Ismaël.

On Sun, Mar 12, 2017 at 9:02 AM, Ahmet Altay 
wrote:

> Amit,
>
> I was able to successfully build in a clean environment with the following
> commands:
>
> git checkout tags/v0.6.0-RC2 -b RC2
> mvn clean install -Prelease
>
> I am not a very familiar with maven build process, it would be great if
> someone else can also confirm this.
>
> Ahmet
>
>
>
> On Sat, Mar 11, 2017 at 11:00 PM, Amit Sela  wrote:
>
> > Building the RC2 tag failed for me with: "mvn clean install -Prelease"
> on a
> > missing artifact "beam-sdks-java-harness" when trying to build
> > "beam-sdks-java-javadoc".
> >
> > I want to make sure It's not something local that happens in my env. so
> if
> > anyone else could validate this it would be great.
> >
> > Amit
> >
> > On Sat, Mar 11, 2017 at 9:48 PM Robert Bradshaw
> > 
> > wrote:
> >
> > > On Fri, Mar 10, 2017 at 9:05 PM, Ahmet Altay  >
> > > wrote:
> > >
> > > > Hi everyone,
> > > >
> > > > Please review and vote on the release candidate #2 for the version
> > 0.6.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 6096FA00 [3],
> > > > * all artifacts to be deployed to the Maven Central Repository [4],
> > > > * source code tag "v0.6.0-RC2" [5],
> > > > * website pull request listing the release and publishing the API
> > > reference
> > > > manual [6].
> > > > * python artifacts are deployed along with the source release to to
> > > > dist.apache.org [2].
> > > >
> > >
> > > Are there plans also to deploy this at PyPi, and if so, what are the
> > > details?
> > >
> > >
> > > > A suite of Jenkins jobs:
> > > > * PreCommit_Java_MavenInstall [7],
> > > > * PostCommit_Java_MavenInstall [8],
> > > > * PostCommit_Java_RunnableOnService_Apex [9],
> > > > * PostCommit_Java_RunnableOnService_Flink [10],
> > > > * PostCommit_Java_RunnableOnService_Spark [11],
> > > > * PostCommit_Java_RunnableOnService_Dataflow [12]
> > > > * PostCommit_Python_Verify [13]
> > > >
> > > > Compared to release candidate #1, this candidate contains pull
> requests
> > > > #2217 [14], #2221 [15], # [16], #2224 [17], and #2225 [18]; see
> the
> > > > discussion for reasoning.
> > > >
> > > > 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?proje
> > > > ctId=12319527=12339256
> > > > [2] https://dist.apache.org/repos/dist/dev/beam/0.6.0/
> > > > [3] https://dist.apache.org/repos/dist/dev/beam/KEYS
> > > > [4]
> > > https://repository.apache.org/content/repositories/orgapachebeam-1013/
> > > > [5] https://git-wip-us.apache.org/repos/asf?p=beam.git;a=tag;h=r
> > > > efs/tags/v0.6.0-RC2
> > > > [6] https://github.com/apache/beam-site/pull/175
> > > > [7] https://builds.apache.org/view/Beam/job/beam_PreCommit_Java_
> > > > MavenInstall/8340/
> > > > [8] https://builds.apache.org/view/Beam/job/beam_PostCommit_
> > > > Java_MavenInstall/2877/
> > > > [9] https://builds.apache.org/view/Beam/job/beam_PostCommit_Java
> > > > _RunnableOnService_Apex/736/
> > > > [10] https://builds.apache.org/view/Beam/job/beam_PostCommit_Java
> > > > _RunnableOnService_Flink/1895/
> > > > [11] https://builds.apache.org/view/Beam/job/beam_PostCommit_Java
> > > > _RunnableOnService_Spark/1207/
> > > > [12] https://builds.apache.org/view/Beam/job/beam_PostCommit_Java_
> > > > RunnableOnService_Dataflow/2526/
> > > > [13] https://builds.apache.org/view/Beam/job/beam_PostCommit_Pyth
> > > > on_Verify/1481/
> > > > [14] https://github.com/apache/beam/pull/2217
> > > > [15] https://github.com/apache/beam/pull/2221
> > > > [16] https://github.com/apache/beam/pull/
> > > > [17] https://github.com/apache/beam/pull/2224
> > > > [18] https://github.com/apache/beam/pull/2225
> > > >
> > >
> >
>

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

[Ahmet Altay]

Amit,

I was able to successfully build in a clean environment with the following
commands:

git checkout tags/v0.6.0-RC2 -b RC2
mvn clean install -Prelease

I am not a very familiar with maven build process, it would be great if
someone else can also confirm this.

Ahmet



On Sat, Mar 11, 2017 at 11:00 PM, Amit Sela  wrote:

> Building the RC2 tag failed for me with: "mvn clean install -Prelease" on a
> missing artifact "beam-sdks-java-harness" when trying to build
> "beam-sdks-java-javadoc".
>
> I want to make sure It's not something local that happens in my env. so if
> anyone else could validate this it would be great.
>
> Amit
>
> On Sat, Mar 11, 2017 at 9:48 PM Robert Bradshaw
> 
> wrote:
>
> > On Fri, Mar 10, 2017 at 9:05 PM, Ahmet Altay 
> > wrote:
> >
> > > Hi everyone,
> > >
> > > Please review and vote on the release candidate #2 for the version
> 0.6.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 6096FA00 [3],
> > > * all artifacts to be deployed to the Maven Central Repository [4],
> > > * source code tag "v0.6.0-RC2" [5],
> > > * website pull request listing the release and publishing the API
> > reference
> > > manual [6].
> > > * python artifacts are deployed along with the source release to to
> > > dist.apache.org [2].
> > >
> >
> > Are there plans also to deploy this at PyPi, and if so, what are the
> > details?
> >
> >
> > > A suite of Jenkins jobs:
> > > * PreCommit_Java_MavenInstall [7],
> > > * PostCommit_Java_MavenInstall [8],
> > > * PostCommit_Java_RunnableOnService_Apex [9],
> > > * PostCommit_Java_RunnableOnService_Flink [10],
> > > * PostCommit_Java_RunnableOnService_Spark [11],
> > > * PostCommit_Java_RunnableOnService_Dataflow [12]
> > > * PostCommit_Python_Verify [13]
> > >
> > > Compared to release candidate #1, this candidate contains pull requests
> > > #2217 [14], #2221 [15], # [16], #2224 [17], and #2225 [18]; see the
> > > discussion for reasoning.
> > >
> > > 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?proje
> > > ctId=12319527=12339256
> > > [2] https://dist.apache.org/repos/dist/dev/beam/0.6.0/
> > > [3] https://dist.apache.org/repos/dist/dev/beam/KEYS
> > > [4]
> > https://repository.apache.org/content/repositories/orgapachebeam-1013/
> > > [5] https://git-wip-us.apache.org/repos/asf?p=beam.git;a=tag;h=r
> > > efs/tags/v0.6.0-RC2
> > > [6] https://github.com/apache/beam-site/pull/175
> > > [7] https://builds.apache.org/view/Beam/job/beam_PreCommit_Java_
> > > MavenInstall/8340/
> > > [8] https://builds.apache.org/view/Beam/job/beam_PostCommit_
> > > Java_MavenInstall/2877/
> > > [9] https://builds.apache.org/view/Beam/job/beam_PostCommit_Java
> > > _RunnableOnService_Apex/736/
> > > [10] https://builds.apache.org/view/Beam/job/beam_PostCommit_Java
> > > _RunnableOnService_Flink/1895/
> > > [11] https://builds.apache.org/view/Beam/job/beam_PostCommit_Java
> > > _RunnableOnService_Spark/1207/
> > > [12] https://builds.apache.org/view/Beam/job/beam_PostCommit_Java_
> > > RunnableOnService_Dataflow/2526/
> > > [13] https://builds.apache.org/view/Beam/job/beam_PostCommit_Pyth
> > > on_Verify/1481/
> > > [14] https://github.com/apache/beam/pull/2217
> > > [15] https://github.com/apache/beam/pull/2221
> > > [16] https://github.com/apache/beam/pull/
> > > [17] https://github.com/apache/beam/pull/2224
> > > [18] https://github.com/apache/beam/pull/2225
> > >
> >
>

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

[Amit Sela]

Building the RC2 tag failed for me with: "mvn clean install -Prelease" on a
missing artifact "beam-sdks-java-harness" when trying to build
"beam-sdks-java-javadoc".

I want to make sure It's not something local that happens in my env. so if
anyone else could validate this it would be great.

Amit

On Sat, Mar 11, 2017 at 9:48 PM Robert Bradshaw 
wrote:

> On Fri, Mar 10, 2017 at 9:05 PM, Ahmet Altay 
> wrote:
>
> > Hi everyone,
> >
> > Please review and vote on the release candidate #2 for the version 0.6.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 6096FA00 [3],
> > * all artifacts to be deployed to the Maven Central Repository [4],
> > * source code tag "v0.6.0-RC2" [5],
> > * website pull request listing the release and publishing the API
> reference
> > manual [6].
> > * python artifacts are deployed along with the source release to to
> > dist.apache.org [2].
> >
>
> Are there plans also to deploy this at PyPi, and if so, what are the
> details?
>
>
> > A suite of Jenkins jobs:
> > * PreCommit_Java_MavenInstall [7],
> > * PostCommit_Java_MavenInstall [8],
> > * PostCommit_Java_RunnableOnService_Apex [9],
> > * PostCommit_Java_RunnableOnService_Flink [10],
> > * PostCommit_Java_RunnableOnService_Spark [11],
> > * PostCommit_Java_RunnableOnService_Dataflow [12]
> > * PostCommit_Python_Verify [13]
> >
> > Compared to release candidate #1, this candidate contains pull requests
> > #2217 [14], #2221 [15], # [16], #2224 [17], and #2225 [18]; see the
> > discussion for reasoning.
> >
> > 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?proje
> > ctId=12319527=12339256
> > [2] https://dist.apache.org/repos/dist/dev/beam/0.6.0/
> > [3] https://dist.apache.org/repos/dist/dev/beam/KEYS
> > [4]
> https://repository.apache.org/content/repositories/orgapachebeam-1013/
> > [5] https://git-wip-us.apache.org/repos/asf?p=beam.git;a=tag;h=r
> > efs/tags/v0.6.0-RC2
> > [6] https://github.com/apache/beam-site/pull/175
> > [7] https://builds.apache.org/view/Beam/job/beam_PreCommit_Java_
> > MavenInstall/8340/
> > [8] https://builds.apache.org/view/Beam/job/beam_PostCommit_
> > Java_MavenInstall/2877/
> > [9] https://builds.apache.org/view/Beam/job/beam_PostCommit_Java
> > _RunnableOnService_Apex/736/
> > [10] https://builds.apache.org/view/Beam/job/beam_PostCommit_Java
> > _RunnableOnService_Flink/1895/
> > [11] https://builds.apache.org/view/Beam/job/beam_PostCommit_Java
> > _RunnableOnService_Spark/1207/
> > [12] https://builds.apache.org/view/Beam/job/beam_PostCommit_Java_
> > RunnableOnService_Dataflow/2526/
> > [13] https://builds.apache.org/view/Beam/job/beam_PostCommit_Pyth
> > on_Verify/1481/
> > [14] https://github.com/apache/beam/pull/2217
> > [15] https://github.com/apache/beam/pull/2221
> > [16] https://github.com/apache/beam/pull/
> > [17] https://github.com/apache/beam/pull/2224
> > [18] https://github.com/apache/beam/pull/2225
> >
>

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

[Robert Bradshaw]

On Fri, Mar 10, 2017 at 9:05 PM, Ahmet Altay 
wrote:

> Hi everyone,
>
> Please review and vote on the release candidate #2 for the version 0.6.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 6096FA00 [3],
> * all artifacts to be deployed to the Maven Central Repository [4],
> * source code tag "v0.6.0-RC2" [5],
> * website pull request listing the release and publishing the API reference
> manual [6].
> * python artifacts are deployed along with the source release to to
> dist.apache.org [2].
>

Are there plans also to deploy this at PyPi, and if so, what are the
details?


> A suite of Jenkins jobs:
> * PreCommit_Java_MavenInstall [7],
> * PostCommit_Java_MavenInstall [8],
> * PostCommit_Java_RunnableOnService_Apex [9],
> * PostCommit_Java_RunnableOnService_Flink [10],
> * PostCommit_Java_RunnableOnService_Spark [11],
> * PostCommit_Java_RunnableOnService_Dataflow [12]
> * PostCommit_Python_Verify [13]
>
> Compared to release candidate #1, this candidate contains pull requests
> #2217 [14], #2221 [15], # [16], #2224 [17], and #2225 [18]; see the
> discussion for reasoning.
>
> 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?proje
> ctId=12319527=12339256
> [2] https://dist.apache.org/repos/dist/dev/beam/0.6.0/
> [3] https://dist.apache.org/repos/dist/dev/beam/KEYS
> [4] https://repository.apache.org/content/repositories/orgapachebeam-1013/
> [5] https://git-wip-us.apache.org/repos/asf?p=beam.git;a=tag;h=r
> efs/tags/v0.6.0-RC2
> [6] https://github.com/apache/beam-site/pull/175
> [7] https://builds.apache.org/view/Beam/job/beam_PreCommit_Java_
> MavenInstall/8340/
> [8] https://builds.apache.org/view/Beam/job/beam_PostCommit_
> Java_MavenInstall/2877/
> [9] https://builds.apache.org/view/Beam/job/beam_PostCommit_Java
> _RunnableOnService_Apex/736/
> [10] https://builds.apache.org/view/Beam/job/beam_PostCommit_Java
> _RunnableOnService_Flink/1895/
> [11] https://builds.apache.org/view/Beam/job/beam_PostCommit_Java
> _RunnableOnService_Spark/1207/
> [12] https://builds.apache.org/view/Beam/job/beam_PostCommit_Java_
> RunnableOnService_Dataflow/2526/
> [13] https://builds.apache.org/view/Beam/job/beam_PostCommit_Pyth
> on_Verify/1481/
> [14] https://github.com/apache/beam/pull/2217
> [15] https://github.com/apache/beam/pull/2221
> [16] https://github.com/apache/beam/pull/
> [17] https://github.com/apache/beam/pull/2224
> [18] https://github.com/apache/beam/pull/2225
>

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

[Ted Yu]

+1

Checked signature.

Ran test suite which passed.

On Fri, Mar 10, 2017 at 9:05 PM, Ahmet Altay 
wrote:

> Hi everyone,
>
> Please review and vote on the release candidate #2 for the version 0.6.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 6096FA00 [3],
> * all artifacts to be deployed to the Maven Central Repository [4],
> * source code tag "v0.6.0-RC2" [5],
> * website pull request listing the release and publishing the API reference
> manual [6].
> * python artifacts are deployed along with the source release to to
> dist.apache.org [2].
>
> A suite of Jenkins jobs:
> * PreCommit_Java_MavenInstall [7],
> * PostCommit_Java_MavenInstall [8],
> * PostCommit_Java_RunnableOnService_Apex [9],
> * PostCommit_Java_RunnableOnService_Flink [10],
> * PostCommit_Java_RunnableOnService_Spark [11],
> * PostCommit_Java_RunnableOnService_Dataflow [12]
> * PostCommit_Python_Verify [13]
>
> Compared to release candidate #1, this candidate contains pull requests
> #2217 [14], #2221 [15], # [16], #2224 [17], and #2225 [18]; see the
> discussion for reasoning.
>
> 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?proje
> ctId=12319527=12339256
> [2] https://dist.apache.org/repos/dist/dev/beam/0.6.0/
> [3] https://dist.apache.org/repos/dist/dev/beam/KEYS
> [4] https://repository.apache.org/content/repositories/orgapachebeam-1013/
> [5] https://git-wip-us.apache.org/repos/asf?p=beam.git;a=tag;h=r
> efs/tags/v0.6.0-RC2
> [6] https://github.com/apache/beam-site/pull/175
> [7] https://builds.apache.org/view/Beam/job/beam_PreCommit_Java_
> MavenInstall/8340/
> [8] https://builds.apache.org/view/Beam/job/beam_PostCommit_
> Java_MavenInstall/2877/
> [9] https://builds.apache.org/view/Beam/job/beam_PostCommit_Java
> _RunnableOnService_Apex/736/
> [10] https://builds.apache.org/view/Beam/job/beam_PostCommit_Java
> _RunnableOnService_Flink/1895/
> [11] https://builds.apache.org/view/Beam/job/beam_PostCommit_Java
> _RunnableOnService_Spark/1207/
> [12] https://builds.apache.org/view/Beam/job/beam_PostCommit_Java_
> RunnableOnService_Dataflow/2526/
> [13] https://builds.apache.org/view/Beam/job/beam_PostCommit_Pyth
> on_Verify/1481/
> [14] https://github.com/apache/beam/pull/2217
> [15] https://github.com/apache/beam/pull/2221
> [16] https://github.com/apache/beam/pull/
> [17] https://github.com/apache/beam/pull/2224
> [18] https://github.com/apache/beam/pull/2225
>