Re: Next major milestone: first stable release

2017-03-01 Thread Jean-Baptiste Onofré
Yes, fully agree. As far as I understood/know, BEAM-59 is targeted for Beam 1.0 (it's what we discussed with Pei and Davor). Regards JB On 03/01/2017 11:39 AM, Ismaël Mejía wrote: Also joining a bit late, I agree with Amit, HDFS improvements are a really good thing to have before the stable

Re: Next major milestone: first stable release

2017-02-28 Thread Davor Bonaci
Alright -- sounds like we have a consensus to proceed with the first stable release after 0.6.0, targeting end of March / early April. I'll kick off separate threads for specific decisions we need to make. On Thu, Feb 23, 2017 at 6:07 AM, Aljoscha Krettek wrote: > I think

Re: Next major milestone: first stable release

2017-02-22 Thread Kenneth Knowles
On Wed, Feb 22, 2017 at 5:35 PM, Chamikara Jayalath wrote: > > I think, this point applies to Python SDK as well (though as you mentioned, > API hiding in Python is a mere convention (prefix with underscore) not > enforced. We already have mechanism for marking APIs as

Re: Next major milestone: first stable release

2017-02-22 Thread Chamikara Jayalath
Great to see Beam API becoming stable and Python SDK becoming a part of it. On Wed, Feb 22, 2017 at 2:57 PM Kenneth Knowles wrote: This is pretty exciting. I'll add thoughts inline. On Tue, Feb 21, 2017 at 6:31 PM, Davor Bonaci wrote: > * Support

Re: Next major milestone: first stable release

2017-02-21 Thread Jean-Baptiste Onofré
Hi Davor, Fully agree. It would be great to have a first 1.0.0 "stable" release in a near future. Thanks ! Regards JB On 02/22/2017 03:31 AM, Davor Bonaci wrote: Graduating from incubation was our single, unifying goal for the past year. With graduation now behind us, I think it is worth