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

By the way, this step is in the "Release Guide". Bu you are right, it means the release manager needs "permission" on the Jira or ask to change the version state. Regards JB On 03/16/2017 02:42 AM, Ahmet Altay wrote: JB, 0.6.0 is flagged as released now, thank you for catching this. As a

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

Thanks ! Regards JB On 03/16/2017 02:42 AM, Ahmet Altay wrote: JB, 0.6.0 is flagged as released now, thank you for catching this. As a side note, I did not have enough permissions do this and asked Davor to do. I will add this to the release notes. Ahmet On Wed, Mar 15, 2017 at 7:16 AM,

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

JB, 0.6.0 is flagged as released now, thank you for catching this. As a side note, I did not have enough permissions do this and asked Davor to do. I will add this to the release notes. Ahmet On Wed, Mar 15, 2017 at 7:16 AM, Jesse Anderson wrote: > Excellent! > > On

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

Excellent! On Wed, Mar 15, 2017, 6:13 AM Jean-Baptiste Onofré wrote: > Hi Ahmet, > > it seems Jira is not up to date: 0.6.0 version is not flagged as > "Released". > > Can you fix that please ? > > Thanks ! > Regards > JB > > On 03/15/2017 05:22 AM, Ahmet Altay wrote: > > I'm

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

Hi Ahmet, it seems Jira is not up to date: 0.6.0 version is not flagged as "Released". Can you fix that please ? Thanks ! Regards JB On 03/15/2017 05:22 AM, Ahmet Altay wrote: I'm happy to announce that we have unanimously approved this release. There are 7 approving votes, 4 of which are

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

Thanks Ahmet for dealing with the release, I just tried the pip install apache-beam and the wordcount example and as you said it feels awesome to see this working so easily now.​ Congrats to everyone working on the python SDK ! On Wed, Mar 15, 2017 at 8:17 AM, Ahmet Altay

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

This release is now complete. Thanks to everyone who have helped make this release possible! Before sending a note to users@, I would like to make a pass over the website and simplify things now that we have an official python release. I did the first 'pip install apache-beam' today and it felt

[RESULT] [VOTE] Release 0.6.0, release candidate #2

I'm happy to announce that we have unanimously approved this release. There are 7 approving votes, 4 of which are binding: * Aljoscha Krettek * Davor Bonaci * Ismaël Mejía * Jean-Baptiste Onofré * Robert Bradshaw * Ted Yu * Tibor Kiss There are no disapproving votes. Thanks everyone! Ahmet

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

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

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

+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

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

+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

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

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: > >

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

+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: > >

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

+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

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

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

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

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

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

​+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

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

+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,

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

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, > > > > > >

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

+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,

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

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

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

+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

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

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 >

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

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

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

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

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

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

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

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

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

+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

[VOTE] Release 0.6.0, release candidate #2

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],