Re: [PROPOSAL] IRC or slack channel for Apache Beam

+1 slack On Wednesday, May 18, 2016, Manu Zhang wrote: > +1 for slack. > > On Wed, May 18, 2016 at 4:41 PM Jean-Baptiste Onofré > > wrote: > > > Good point Robert. > > > > I will be on the channel for sure (I'm already on bunch of Apache IRC > > channels ;)). > > > > Regards > > JB > > > > On 0

Re: [DISCUSS] Developing new components -- branches, maturity, and committers

+1, this is a step in the right direction. On Wed, May 18, 2016 at 10:02 PM Frances Perry wrote: > Hi Beamers -- > > I’m thrilled by the recent energy and activity on writing new Beam runners! > But that also means it’s probably time for us to figure out how, as a > community, we want to support

Dynamic work rebalancing for Beam

Hey folks, This morning, my colleagues Eugene & Malo posted *No shard left behind: dynamic work rebalancing in Google Cloud Dataflow *. This article discusses Cloud Dataflow’s sol

[DISCUSS] Developing new components -- branches, maturity, and committers

Hi Beamers -- I’m thrilled by the recent energy and activity on writing new Beam runners! But that also means it’s probably time for us to figure out how, as a community, we want to support this process. ;-) Back near the beginning, we had a thread [1] discussing that feature branches are the pre

Re: [PROPOSAL] IRC or slack channel for Apache Beam

+1 for slack. On Wed, May 18, 2016 at 4:41 PM Jean-Baptiste Onofré wrote: > Good point Robert. > > I will be on the channel for sure (I'm already on bunch of Apache IRC > channels ;)). > > Regards > JB > > On 05/18/2016 10:26 AM, Robert Bradshaw wrote: > > The value in such a channel is highly d

Re: [UPDATE] 0.1-incubating version created in Jira

Thanks for the version number fix. So, it means that later, if an user will check Jira, he will have to know that blank means "fixed in 0.1.0-incubating". If we agree about that, that's fine (I prefer explicit fixed version, but I don't mind ;)). Regards JB On 05/18/2016 06:05 PM, Davor Bo

Build failed in Jenkins: beam_Release_NightlySnapshot #45

See Changes: [mxm] [flink] replace obsolete reflection call [dhalperi] Pub/sub unbounded source -- [...truncated 3875 lines...] [INFO] Uploaded: https://repository.apache.org/content

[UPDATE] 0.1-incubating version created in Jira

Hi all, I created 0.1-incubating version in Jira. As we are going to use it to generate the RELEASE NOTES, it would be great if you can review the open Jira and define the fix version field if you want to include it in first 0.1-incubating release. I plan to do a bulk change to assign this f

Re: [PROPOSAL] IRC or slack channel for Apache Beam

Good point Robert. I will be on the channel for sure (I'm already on bunch of Apache IRC channels ;)). Regards JB On 05/18/2016 10:26 AM, Robert Bradshaw wrote: The value in such a channel is highly dependent on people regularly being there--do we have a critical mass of developers that woul

Re: [PROPOSAL] IRC or slack channel for Apache Beam

The value in such a channel is highly dependent on people regularly being there--do we have a critical mass of developers that would hang out there? If so, I'd say go for it. On Wed, May 18, 2016 at 12:51 AM, Amit Sela wrote: > +1 for Slack > > On Wed, May 18, 2016 at 10:47 AM Jean-Baptiste Onofr

Re: [PROPOSAL] IRC or slack channel for Apache Beam

+1 for Slack On Wed, May 18, 2016 at 10:47 AM Jean-Baptiste Onofré wrote: > Hi all, > > What do you think about creating a #apache-beam IRC channel on freenode > ? Or if it's more convenient a channel on Slack ? > > Regards > JB > -- > Jean-Baptiste Onofré > jbono...@apache.org > http://blog.nan

[PROPOSAL] IRC or slack channel for Apache Beam

Hi all, What do you think about creating a #apache-beam IRC channel on freenode ? Or if it's more convenient a channel on Slack ? Regards JB -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com