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

Hi Ahmet, sorry I missed those Jira. Can you help to cherry-pick and fix both issues on release-2.1.0 branch ? The release guide already mention to check to open Jira on the release target. I just missed these two Jira, sorry about that. I don't think an additional list is required. I will

Groovy Expertise?

Hey all, If anyone has experience working with Groovy, I would love for someone to take a look at https://github.com/apache/beam/pull/3545, which does a decent amount of work with the Jenkins Job DSL in preparation for some precommit changes. Thanks, Jason -- --- Jason Kuster Apache Beam

Re: Java 8?

Recently on Spark and Flink mailing lists there have been discussion on dropping support for Java 7. For master branch, we should consider moving to Java 8 for compilation. On Fri, Jul 14, 2017 at 2:41 PM, Swapnil Bawaskar wrote: > Hi, > > I am trying to write a write an

Re: MergeBot is here!

I think 1 & 3 can be squashed :-) If someone has fixup! commits you definitely don't want to merge exactly as-is so it shouldn't be possible. (and if they messed up their fixup! so it doesn't vanish, you also don't want to merge that) And then, yes, that covers my wants. On Fri, Jul 14, 2017 at

Re: MergeBot is here!

Hey folks, thanks for your thoughts! I have some responses for you. :) Regarding squashing, it looks like there are three things at play -- forgive me if I've misunderstood. 1. Merge commits exactly as they are in the PR. 2. Squash all commits down to the first commit 3. Automatically squash

Java 8?

Hi, I am trying to write a write an I/O transform for Apache Geode, which is compiled with java-8. When I try to compile what I have so far, I get the following error: [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce) @ beam-sdks-java-io-geode --- [INFO] Restricted to JDK 1.7 yet

Re: [DISCUSS] Beam MapReduce Runner One-Pager

Thanks Pei, left a few comments, but this looks exciting! -Vikas On 12 July 2017 at 21:52, Jean-Baptiste Onofré wrote: > Hi, > > I will push my branch with the current state of the mapreduce runner. > > Regards > JB > > > On 07/13/2017 04:47 AM, Pei HE wrote: > >> Thanks

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

These are good points which I agree with. We should have an empty burndown list so people trust that flagging an issue will not be ignored. BEAM-2595: this actually got added to the burndown after the RC was cut. Maybe next time send a mail to the [DISCUSS] thread right away? Otherwise someone

Pull requests for review

Hi, Could someone please review my PR's and let me know if any changes: https://github.com/apache/beam/pull/3526 https://github.com/apache/beam/pull/3534 https://github.com/apache/beam/pull/3535 Thanks, Almas

Re: Starter Issue for New Contributor

Thanks Kenn, I guess I got a bit too excited to start - I notice that this step is clearly marked in the Contributor Guide, no more tl;dr for me - digging into the whole doc :)) On Fri, Jul 14, 2017 at 10:42 AM, Kenneth Knowles wrote: > If you haven't worked through >

Re: Starter Issue for New Contributor

If you haven't worked through https://beam.apache.org/contribute/contribution-guide/, please do! But anyhow you are doing all the right things - most importantly, joining the dev list and asking :-) Now a committer needs to add you as a "Contributor" in JIRA before you can be assigned or take

Re: Starter Issue for New Contributor

For example: I want to work on https://issues.apache.org/jira/browse/BEAM-2492 And i'd like it assigned to myself, don't really see an option on the webpage. On Fri, Jul 14, 2017 at 10:04 AM, Sugata Acharjya wrote: > Awesome, thanks! Once I've found an issue I want to work

Re: Starter Issue for New Contributor

Awesome, thanks! Once I've found an issue I want to work on, how would I get it assigned to myself? On Fri, Jul 14, 2017 at 9:46 AM, Apache Enthu wrote: > Try to search for issue in jira with label as newbie. > > Thanks, > Almas > > On 14 Jul 2017 18:37, "Sugata Acharjya"

Starter Issue for New Contributor

Hi, I'm looking to get started on contributing this weekend. Can somebody point me to an issue (trivial/small) to that'd be a good way to get started? Appreciate it, thanks! -- Regards, Sugata Acharjya Cell: (416) 809-3921

Re: Regarding Beam Slack Channel

Yup thanks! On Thu, Jul 13, 2017 at 10:07 PM, Lukasz Cwik wrote: > Someone sent an invite already. Were you able to use it successfully? > > On Thu, Jul 13, 2017 at 2:37 PM, Sugata Acharjya > wrote: > > > Hello > > > > Can someone please add me to