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

2017-03-14 Thread Ahmet Altay
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

2017-03-14 Thread Ahmet Altay
t; > > > > wrote: > > > > > > > > +Stas Levin <stasle...@apache.org> +Thomas Groh <tg...@google.com> > > > > > > > > On Mon, Mar 13, 2017 at 5:30 PM Eugene Kirpichov < > kirpic...@google.com > > > > > > &g

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

2017-03-12 Thread Ahmet Altay
shall not hold up the release. > > Thanks for putting this RC together! > > - Tibor > > On 3/11/17, 6:05 AM, "Ahmet Altay" <al...@google.com.INVALID> wrote: > > Hi everyone, > > Please review and vote on the release candidate #2 for the version &

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

2017-03-12 Thread Ahmet Altay
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 > <rober...@google.com.invalid> > wrote: > > > On Fri, Mar 10, 2017 at 9:05 PM, Ahmet Altay

[VOTE] Release 0.6.0, release candidate #2

2017-03-10 Thread Ahmet Altay
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],

Re: First time PR question: Multiple issues addressed in single change

2017-03-10 Thread Ahmet Altay
Hi Ankur On Fri, Mar 10, 2017 at 6:08 PM, Ankur Chauhan wrote: > Hi all, > > This is my first go at contributing some simple changes to the BigTableIO > in beam. The main intent was to update the dependency to 0.9.5.1 from the > current 0.9.2 which would address some changes

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

2017-03-10 Thread Ahmet Altay
Let's cancel the vote on RC1 and I will start a new one. I think Davor had a great summary and I will make those changes for RC2. I only have one comment, I would rather keep a single file format (.zip) instead of using both file formats (.zip, .tar.gz). I think this is better for having a single

[VOTE] Release 0.6.0, release candidate #1

2017-03-09 Thread Ahmet Altay
Hi everyone, Please review and vote on the release candidate #1 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], *

Re: Release 0.6.0

2017-03-01 Thread Ahmet Altay
B > > > On 03/01/2017 07:23 PM, Ahmet Altay wrote: > >> Thank you. I will start working on it. >> >> Ahmet >> >> On Wed, Mar 1, 2017 at 9:03 AM, Aljoscha Krettek <aljos...@apache.org> >> wrote: >> >> I just closed the last blocking is

Re: Release 0.6.0

2017-02-28 Thread Ahmet Altay
>>> I also try to merge https://github.com/apache/beam/pull/1739 asap. > > >>> > > >>> Regards > > >>> JB > > >>> > > >>> On 02/28/2017 09:34 AM, Amit Sela wrote: > > >>>> I'd prefer we wait to merge htt

Release 0.6.0

2017-02-27 Thread Ahmet Altay
Hi all, It's been about a month since the last release. I would like propose starting the next release. There are no releasing blocking bugs in JIRA [1]. Are there any release blocking issues I am missing? Unless there is an objection I will volunteer to manage this release. This will be the

tf.Transform library for using TensorFlow with Beam

2017-02-23 Thread Ahmet Altay
Hi all, Yesterday, there was an announcement from TensorFlow community about the new tf.Transform library [1]. It is a library that allows users to define pre-processing pipelines and run using large scale data processing frameworks. It is a library specifically designed to work with Apache Beam.

Re: Build failed in Jenkins: beam_PostCommit_Python_Verify #1308

2017-02-19 Thread Ahmet Altay
I am looking at this right now, It is caused by https://github.com/apache/ beam/pull/2041. https://github.com/apache/beam/pull/2045 has a fix. Thank you, Ahmet On Sun, Feb 19, 2017 at 12:13 AM, Jean-Baptiste Onofré wrote: > It seems Python build is failing. > > Gonna take a

Re: [DISCUSS] Python SDK status and next steps

2017-01-31 Thread Ahmet Altay
ed by the default "regular" build. >>>>> >>>>> Regards >>>>> JB >>>>> >>>>> >>>>> On 01/31/2017 11:02 AM, Jean-Baptiste Onofré wrote: >>>>> >>>>> Just one thing

Re: [DISCUSS] Python SDK status and next steps

2017-01-30 Thread Ahmet Altay
es, which was deferred while > > seeing how https://s.apache.org/splittable-do-fn played out. I've been > > working with the team and merging/reviewing most of their code, and > > have full confidence this will be coming (and on that note can vouch > > for a healthy community and s

Re: Build failed in Jenkins: beam_PostCommit_Python_Verify #1111

2017-01-29 Thread Ahmet Altay
4 tests failed due to quota errors with project resources. I do not see any more quota errors on the project, this should fix itself in the next run. Ahmet On Sun, Jan 29, 2017 at 1:12 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See

Re: [ANNOUNCEMENT] New committers, January 2017 edition!

2017-01-27 Thread Ahmet Altay
ooking at code contributions > > > >alone, he authored 43 commits and reported 25 issues. Stas is very > > > >active > > > >on the mailing lists too, contributing to good discussions and > > > >proposing > > > >improvements to the Beam model. > > &

Re: [VOTE] Merge Python SDK to the master branch

2017-01-23 Thread Ahmet Altay
is more important. > > > > > > On Mon, Jan 23, 2017 at 8:36 AM, Sergio Fernández <wik...@apache.org> > > > wrote: > > > > > > > +1 > > > > > > > > On Fri, Jan 20, 2017 at 9:24 PM, Robert Bradshaw <

Re: [DISCUSS] Python SDK status and next steps

2017-01-20 Thread Ahmet Altay
fleshed > out soon; including potentially new users/contributors that would arrive > once in master. > > [1] https://lists.apache.org/thread.html/CAAzyFAxcmexUQnbF=Y > k0plmm3f5e5bqwjz4+c5doruclnxo...@mail.gmail.com > > On Wed, Jan 18, 2017 at 12:24 AM, Ahmet Altay <al...@google

Re: [DISCUSS] Python SDK status and next steps

2017-01-18 Thread Ahmet Altay
Thank you all for the comments so far. I would follow the process as suggested by Davor and others in this thread. Ahmet On Tue, Jan 17, 2017 at 11:47 PM, Sergio Fernández <wik...@apache.org> wrote: > Hi > > On Tue, Jan 17, 2017 at 5:22 PM, Ahmet Altay <al...@google.co

<    5   6   7   8   9   10