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

2019-02-26 Thread Konstantinos Katsiapis
+1. (Same rational as my earlier post for RC1). On Tue, Feb 26, 2019 at 2:19 AM Maximilian Michels wrote: > +1 (binding) > > * Verified checksums > * Ran quickstart WordCount tests local/cluster with the Flink Runner > > -Max > > On 26.02.19 10:40, Ahmet Altay wrote: > > Hi everyone, > > > > Ple

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

2019-02-24 Thread Konstantinos Katsiapis
+1 We (TFX ) are really looking forward to the Python 3 compatibility that Apache Beam 2.11 brings. The 2.11 release will allow several of our existing Apache Beam based libraries like TensorFlow Data Validation ,

Re: [VOTE] Release 2.4.0, release candidate #3

2018-03-19 Thread Konstantinos Katsiapis
+1, since Tf.Transform 0.6 depends on (and is blocked by) Beam 2.4 On Sat, Mar 17, 2018 at 2:19 AM, Robert Bradshaw wrote: > Hi everyone, > > Please review and vote on the release candidate #3 for the version 2.4.0, > as follows: > [ ] +1, Approve the re

Re: Beam 2.4.0

2018-02-28 Thread Konstantinos Katsiapis
Hi Jean-Baptiste, I can speak from the perspective of tf.transform (TFT) in particular and TFX libs in general, in case it is useful. TFX distributed computation has 2 "large" dependencies, namely TensorFlo

Re: Beam 2.4.0

2018-02-20 Thread Konstantinos Katsiapis
+1 since tf.transform 0.6 depends on Beam 2.4 and Tensorflow 1.6 (and the latter already has an RC out, so we will likely be blocked on Beam). On Tue, Feb 20, 2018 at 12:50 PM, Robert Bradshaw wrote: > Now that Beam 2.3.0 went out (and in record time, ku

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

2018-01-31 Thread Konstantinos Katsiapis
+1 (non-binding). tensorflow.transform 0.5.0 is blocked on Apache Beam 2.3 On Wed, Jan 31, 2018 at 5:59 AM, Jean-Baptiste Onofré wrote: > +1 (binding) > > Casting my own +1 ;) > > Regards > JB > > On 01/30/2018 09:04 AM, Jean-Baptiste Onofré wrote: > >

Re: [DISCUSS] Towards Beam 2.3.0

2018-01-09 Thread Konstantinos Katsiapis
+1 Our team works on tensorflow.transform (which depends on Apache Beam) and a regular Beam release cadence would make our releases a lot easier (eg our 0.5 release will likely require and depend on Beam 2.3). Is the plan to make "regular" something like

Re: [VOTE] Release 2.2.0, release candidate #4

2017-11-22 Thread Konstantinos Katsiapis
+1 (non-binding) Since Beam 2.2 is blocking release of tensorflow.transform 0.4. On Wed, Nov 22, 2017 at 10:19 AM, Nishu wrote: > Hi, > > Typo in previous mail. I meant Flink runner. > > Thanks, > Nishu > On Wed, 22 Nov 2017 at 19.17, > > > Hi, > > > >

Re: [VOTE] Release 2.2.0, release candidate #3

2017-11-09 Thread Konstantinos Katsiapis
Just a remark: Release of Tensorflow Transform 0.4.0 depends on release of Apache Beam 2.2.0 so upvoting for a release (the sooner the better). On Thu, Nov 9, 2017 at 3:33 PM, Reuven Lax wrote: > Are we waiting for any more validation of this candidate?