Re: [VOTE] Release Apache Beam, version 0.2.0-incubating

+1 (binding) - built from source - “incubating” in file name - NOTICE and LICENSE look good - license headers present - no wayward binaries - signatures check out -Taylor > On Aug 1, 2016, at 12:46 PM, Dan Halperin wrote: > > Hey folks! > > Here's the vote for

Utility for Serializing PipelineOptions

Looking at the runner implementations for Spark, Flink, and Gearpump, they all have the same requirement of being able to serialize/deserialize PipelineOptions, and they each seem to use slightly different approaches. In working on a Beam runner for Storm I have the same requirement, and

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

Can I get an invite to the slack channel? I’m in the early stages of implementing a Beam runner for Apache Storm and have some (probably stupid ;) ) questions. Also, would it make sense to document the process on the Beam website so new users/devs can find out about it and how to join?

Re: 0.1.0-incubating release

ServiceMix, etc. > > Regards > JB > > On 06/08/2016 02:39 AM, P. Taylor Goetz wrote: >> Out of curiosity, is there a reason for distributing the release on >> repository.a.o vs. dist.a.o? >> >> In my experience repository.a.o has traditionally been used for

Re: 0.1.0-incubating release

Out of curiosity, is there a reason for distributing the release on repository.a.o vs. dist.a.o? In my experience repository.a.o has traditionally been used for maven artifacts, and dist.a.o has been for release artifacts (source archives and convenience binaries). I'd be happy to help with

Re: Permission problems

Any of your mentors ought to be able to take care of this for you. When you need help from mentors, it sometimes helps to prepend “[MENTORS]” to the subject to get their attention. -Taylor > On Mar 4, 2016, at 4:17 PM, Davor Bonaci wrote: > > This is something that