Re: [DISCUSS] Python SDK status and next steps

Great -- congratulations to everyone who has contributed to the Python SDK! On Mon, Jan 30, 2017 at 11:10 PM, Ahmet Altay wrote: > Hi all, > > This merge is completed. Python SDK is now officially part of the master > branch! Thank you all for the support. Please open

Re: Beam connector development for Hive as a data source

Hi Madhu, Welcome! I suggest subscribing to the dev@ mailing list and using the same email address when sending to the list, to avoid your email being caught in moderation. It would be great to have a connector for Apache Hive. Keep in mind that several folks have expressed interest in using and

Report to the Board, February 2017 edition

We are expected to submit a project report to the ASF Board of Directors ahead of its next meeting. The report is due on Wednesday, 2/8. This is the second is the series of three monthly reports required for new projects. We'll need to report next month as well. If interested, please take a look

Re: [RESULT] [VOTE] Apache Beam, version 0.5.0, release candidate #2

This release is now complete. Thanks to everyone who have helped make this release possible! On Mon, Feb 6, 2017 at 8:36 AM, Davor Bonaci <da...@apache.org> wrote: > I'm happy to announce that we have unanimously approved this release. > > There are 5 approving votes, 4 of wh

Re: [VOTE] Apache Beam, version 0.5.0, release candidate #2

ng the release, since git tags can be changed. Just take that into > account for upcoming releases. > > > On Fri, Feb 3, 2017 at 1:27 AM, Davor Bonaci <da...@apache.org> wrote: > > > Hi everyone, > > With JB leaving for his vacation, I'll try to push the 0.5.0 release &g

Re: BEAM-307(KafkaIO on Kafka 0.10)

This would be a great contribution, Mingmin! As a general rule, we'd like the connector to work with as many versions as possible, with as little code duplication as possible. Slightly orthogonal -- BigtableIO [1] is an example of a connector that separates API portions from the underlying

Re: Subscription to to beam project

Welcome! Please check out the support page [1] with all mailing lists and subscribe links. [1] https://beam.apache.org/get-started/support/ On Sat, Jan 21, 2017 at 11:59 PM, Ritesh Kasat wrote: > Hello, > Please add me to the beam mailing list. > Thanks > Ritesh >

Re: [VOTE] Apache Beam, version 0.5.0, release candidate #1

It looks good to me, but let's hear Aljoscha's opinion on BEAM-1346. A passing suite of Jenkins jobs: * https://builds.apache.org/job/beam_PreCommit_Java_MavenInstall/6870/ * https://builds.apache.org/job/beam_PostCommit_Java_MavenInstall/2474/ *

Next major milestone: first stable release

Graduating from incubation was our single, unifying goal for the past year. With graduation now behind us, I think it is worth looking ahead towards the next major milestone: the first stable release. I think the first stable release is the logical next step. It enables the growth of our user

Re: Beam on Kubernetes

I think these are great ideas for simplifying the getting started experience across runners -- we'd love a contribution in this space! On Mon, Feb 20, 2017 at 12:46 AM, Jean-Baptiste Onofré wrote: > Hi Nitin, > > It sounds like a good candidate for blog or documentation, or

Re: Interest in a (virtual) contributor meeting?

>> בתאריך 22 בפבר' 2017 2:54 PM,‏ "Aljoscha Krettek" <aljos...@apache.org> >>> כתב: >>> >>> +1 >>>> >>>> On Wed, 22 Feb 2017 at 10:08 JingsongLee <lzljs3620...@aliyun.com> >>>> >>> wrote: &

Re: tf.Transform library for using TensorFlow with Beam

Beam and TensorFlow coming together -- a big deal for us! On Thu, Feb 23, 2017 at 3:49 PM, Ahmet Altay wrote: > Hi all, > > Yesterday, there was an announcement from TensorFlow community about the > new tf.Transform library [1]. It is a library that allows users to

Re: Better developer instructions for using Maven?

I think Dan's framework of thinking is right -- what is the probability of something finding a real issue, vs. the cost of running that all the time. Obviously, we cannot run *everything* all the time. There's an infinite number of things to run and infinite matrix of configurations. Many tests

Release 0.5.0

It's been about a month since the last release, so we should start preparing the next one. We have plenty of great content to share with our users! We have a couple of release blocking bugs [1], but they seem to be heading towards a conclusion. Is anybody aware of any other release blocking

Re: [DISCUSS] Python SDK status and next steps

+1. I think merging to master would be an awesome next step for the Python SDK. And, thanks for a great summary of the current state, roadmap, and impact to the project as a whole -- awesome! Process-wise, I'd suggest starting a formal vote once this discussion seems to be trending towards a

Re: [VOTE] Merge Python SDK to the master branch

[X] +1, Merge python-sdk branch to master after the 0.5.0 release, and release it in the subsequent minor release. On Fri, Jan 20, 2017 at 9:03 AM, Ahmet Altay wrote: > Hi all, > > > Please review the earlier discussion on the status of the Python SDK [1] > and vote

Re: Release 0.6.0

Can we please use JIRA to tag potentially release-blocking issues? Anyone can just add a 'Fix Versions' field of an open issue to the next scheduled release -- and it becomes easily visible to everyone in the project. In general, I'm not a fan of blocking releases for new functionality. Rushing

Re: Next major milestone: first stable release

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: tf.Transform library for using TensorFlow with Beam

ized', and > > > 'x_centered_times_y_normalized' keys > > > # with the expected values, and fn can be used to transform other data > > > using the > > > # statistics (mean, mins, and maxes) without re-analysis. > > > output, fn = (input, schema) | &

Re: Starter issue

Welcome Tim -- it's great to have you join our community! I found your name in JIRA and assigned the issue to you. Thanks for your (future) contribution. On Wed, Jan 11, 2017 at 11:27 PM, Jean-Baptiste Onofré wrote: > Hi Tim > > What's your Jira id ? > > Thanks > Regards >

Re: [DISCUSS] Graduation to a top-level project

gt; > Regards > JB > > On 12/28/2016 07:22 AM, Davor Bonaci wrote: > >> As part of the process, Apache Infra should be reconfiguring our DNS >> records, repository URLs, mailing list addresses, etc. shortly. Please >> expect some instability over the next several day

Re: Azure Blob IO for Apache Beam

Hi Saulo, I've responded to your Stack Overflow question, but I can give a few more comments here. Pei (cc'd) is working on this. See this JIRA issue [1], its sub-tasks, and several design documents [2, 3]. It would be awesome to also have native Azure Storage Blob support in Beam that builds on

Re: Please make sure you unincubate

The Incubator website has been updated [1, 2], and INFRA-13177 is tracking the infrastructure work [3]. Special thanks to JB and Dan for handling some parts of the work. John, please kindly let us know if you spot something we may have missed. Davor [1] http://incubator.apache.org/projects/ [2]

[ANNOUNCEMENT] New committers, March 2017 edition!

Please join me and the rest of Beam PMC in welcoming the following contributors as our newest committers. They have significantly contributed to the project in different ways, and we look forward to many more contributions in the future. * Chamikara Jayalath Chamikara has been contributing to

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

+1 (binding) Contingent on adding NOTICE and LICENSE files into "apache-beam-0.6.0-python.zip", just as they are present in the "apache-beam-0.6.0-source-release.zip". On Tue, Mar 14, 2017 at 10:02 AM, Aljoscha Krettek wrote: > +1 (binding) > > - verified release signature

Re: Apache Beam (virtual) contributor meeting @ Tue Mar 7, 2017

2017 at 3:20 AM, Davor Bonaci <da...@apache.org> wrote: > > > Link: https://hangouts.google.com/hangouts/_/google.com/beam-dev-mtg > > > > I'll try to be available on Slack shortly before the meeting, just in > case > > someone has trouble connecting. > &g

Re: JStorm runner

Also, JIRA component created [1], with Pei as component lead. Davor [1] https://issues.apache.org/jira/browse/BEAM/component/12332477/?selectedTab=com.atlassian.jira.jira-projects-plugin:component-summary-panel On Thu, Apr 6, 2017 at 7:55 PM, Kenneth Knowles wrote: >

Re: Apache Storm/JStorm Runner(s) for Apache Beam

This is a great discussion; thanks everyone. >From my perspective, the functionality to execute pipelines on both Storm and JStorm is very welcome and a big step forward for Beam. I'm not an expert on the Storm/JStorm differences, but one vs. two runners discussion sounds more like a packaging /

Re: Build failed in Jenkins: beam_SeedJob #209

Something has changed on the infrastructure side; looking... On Sun, Apr 16, 2017 at 11:02 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See > > -- > [...truncated 263.39

Re: Build failed in Jenkins: beam_SeedJob #214

Not so simple, unfortunately [1]. Ideas welcome ;-) Davor [1] https://github.com/jenkinsci/job-dsl-plugin/wiki/Migration#migrating-to-160 On Tue, Apr 18, 2017 at 9:57 AM, Ted Yu wrote: > I wonder if we should adopt the suggestion here (involving evaluate): >

Re: Hanging Jenkins builds.

Intermittent hanging exist for several days, maybe up to a week. I think it correlates with updates/restarts/reconfiguration/etc. of the Jenkins instance on the infrastructure side. Terminating the build and restarting did work around the problem a few times. On Sat, Apr 22, 2017 at 9:42 AM, Ted

Re: [PROPOSAL] Remove KeyedCombineFn

+1 -- this is a good simplification. On Fri, Apr 21, 2017 at 10:24 AM, Kenneth Knowles wrote: > Hi all, > > I propose that we remove KeyedCombineFn before the first stable release. > > I don't think it adds enough value for the complexity it adds to e.g. >

Re: Add GitHub topics to Beam repository

We certainly cannot do this ourselves, but it is within the realm of possibility that Apache Infra can assign tags to our GitHub repositories. Looking at the tags that already exist, perhaps we could go with: * apache-beam * big-data * data-processing * data-analysis * data-science *

Re: [PROPOSAL] Add 2.0.0 version in Jira

I added "First stable release" in JIRA as a version identifier a while back, to avoid any prejudice what that version might be called. I think it makes sense to resolve (newly fixed) issues against that version. Once we finalize the name of that release, we can easily rename it to either "1.0.0"

Re: Report to the Board, March 2017 edition

The report is now submitted; thanks for the comments and improvements! On Tue, Mar 7, 2017 at 6:14 PM, Davor Bonaci <da...@apache.org> wrote: > We are expected to submit a project report to the ASF Board of Directors > ahead of its next meeting. The report is due on We

Re: Apache Beam (virtual) contributor meeting @ Tue Mar 7, 2017

Just a remainder that this is happening in about ~22 hours from now. Hope to see all of you there. On Thu, Mar 2, 2017 at 4:22 PM, Davor Bonaci <da...@apache.org> wrote: > I'd prefer not to record the video; just to keep things informal. We'll, > however, keep the notes and sh

Fwd: Google Summer of Code 2017 Mentor Registration

There was a previous discussion and planning around Beam's involvement with the Summer of Code 2017 -- here's more information on how to get started and formally register as a mentor. Davor -- Forwarded message -- From: Ulrich Stärk Date: Mon, Mar 6, 2017 at

Re: First stable release: version designation?

; > > > However, as Dataflow SDK (origins of Beam) was in 1.0.0, in order to > > avoid confusion with users coming to Beam from Dataflow, 2.0.0 could > help. > > > > I have a preference to 1.0.0 anyway, but I would understand starting > > from 2.0.0. > > > >

Re: Apache Beam (virtual) contributor meeting @ Tue Mar 7, 2017

together. > > On Mon, Mar 6, 2017 at 7:23 PM Davor Bonaci <da...@apache.org> wrote: > > > Just a remainder that this is happening in about ~22 hours from now. Hope > > to see all of you there. > > > > On Thu, Mar 2, 2017 at 4:22 PM, Davor Bonaci <da...@ap

Re: found a typographical error in the Beam documentation.

Indeed -- there's a typo on that page. Would you be willing to submit a pull request to our website repository [1] correcting this? Thanks! Davor [1] https://github.com/apache/beam-site On Tue, Mar 7, 2017 at 12:28 AM, 성준영 wrote: > In Beam Documentation - Programming

First stable release: version designation?

The first stable release is our next major project-wide goal; see discussion in [1]. I've been referring to it as "the first stable release" for a long time, not "1.0.0" or "2.0.0" or "2017" or something else, to make sure we have an unbiased discussion and a consensus-based decision on this

Apache Beam (virtual) contributor meeting @ Tue Mar 7, 2017

...@google.com ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP= TRUE;CN=dev@beam.apache.org;X-NUM-GUESTS=0:mailto:dev@beam.apache.org ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE ;CN=Davor Bonaci;X-NUM-GUESTS=0:mailto:da...@google.com CREATED

Re: found a typographical error in the Beam documentation.

apache_beam_doc_ko>. If you are > interested, it would be a great honor for me. > > Thanks for the quick answer :) > > > 켜짐 2017년 3월 7일 에서 오후 11:50:58, Davor Bonaci (da...@apache.org) 작성됨: > > Indeed -- there's a typo on that page. > > Would you be willing to subm

Report to the Board, March 2017 edition

We are expected to submit a project report to the ASF Board of Directors ahead of its next meeting. The report is due on Wednesday, 3/8. This is the third is the series of three consecutive monthly reports required for new projects. If interested, please take a look at the draft [1], and comment

[ANNOUNCEMENT] New committers, August 2017 edition!

Please join me and the rest of Beam PMC in welcoming the following contributors as our newest committers. They have significantly contributed to the project in different ways, and we look forward to many more contributions in the future. * Reuven Lax Reuven has been with the project since the

[ANNOUNCEMENT] New PMC members, August 2017 edition!

Please join me and the rest of Beam PMC in welcoming the following committers as our newest PMC members. They have significantly contributed to the project in different ways, and we look forward to many more contributions in the future. * Ahmet Altay Beyond significant work to drive the Python

Re: MergeBot is here!

This is fantastic! Thank you Jason, and special thanks to the Infrastructure team for supporting us every step of the way. On Fri, Jul 7, 2017 at 1:21 PM, Jason Kuster wrote: > Hi Beam Community, > > Early on in the project, we had a number of discussions about

Re: Community hackathon

The outage is still ongoing, unfortunately... I think we should make one more (and final) delay. New (final) start time: 11 PM Pacific, and we start regardless of the outage. On Wed, Apr 26, 2017 at 10:04 AM, Davor Bonaci <da...@apache.org> wrote: > *** DELAYED START *** > > Unf

Re: Community hackathon

! Davor On Wed, Apr 26, 2017 at 2:02 PM, Davor Bonaci <da...@apache.org> wrote: > The outage is still ongoing, unfortunately... I think we should make one > more (and final) delay. > > New (final) start time: 11 PM Pacific, and we start regardless of the > outage. > > On We

Community hackathon

We've been working as a community towards the first stable release for a while now, and I think we made a ton of progress across the board over the last few weeks. We could try to organize a community-wide hackathon to identify and fix those last few issues, as well as to get a better sense of

Re: Community hackathon

gt; > > > > On Apr 24, 2017 12:51 AM, "Jean-Baptiste Onofré" <j...@nanthrax.net> > > wrote: > > > > > > > That's a wonderful idea ! > > > > > > > > I think the easiest way to organize this event is using the Slack > > > chan

Re: First stable release: release candidate #3

This RC is now obsolete -- see RC #4 information with a formal vote in a separate thread [1]. Davor [1] https://lists.apache.org/thread.html/8cf5d7583111f7d67bd21918eb35a29823572ad9ebc1d6df9656bc79@%3Cdev.beam.apache.org%3E On Fri, May 12, 2017 at 12:57 AM, Davor Bonaci <da...@apache.org>

[VOTE] First stable release: release candidate #4

Hi everyone -- After going through several release candidates, setting and validating acceptance criteria, running a hackathon, and polishing the release, now is the time to vote! Please review and vote on the release candidate #4 for the version 2.0.0, as follows: [ ] +1, Approve the release [ ]

First stable release: release candidate #3

The release candidate #3 for the version 2.0.0 has been built. I think this candidate could be it -- we have cleared the entire list of blocking changes [8]! I'd like to ask everyone to give this candidate a try -- this is the last opportunity we have to fix any critical issues if the final

Re: First stable release: release candidate #2

This RC is now obsolete -- see RC #3 information in a separate thread [1]. Davor [1] https://lists.apache.org/thread.html/25493fded77367299ad185c308d658eeb10e4f03be725154b0e5b08d@%3Cdev.beam.apache.org%3E On Wed, May 10, 2017 at 10:28 PM, Davor Bonaci <da...@apache.org> wrote: > Th

Re: First stable release: release candidate #1

This RC is now obsolete -- see RC #2 information in a separate thread [1]. Davor [1] https://lists.apache.org/thread.html/f4f13f8b4768d0597e7f0c60a0b4d4358c4b8cbc4af86f17f58a1a4d@%3Cdev.beam.apache.org%3E On Mon, May 8, 2017 at 1:59 PM, Davor Bonaci <da...@apache.org> wrote: > Th

First stable release: release candidate #2

The release candidate #2 for the version 2.0.0 has been built. I believe this is a pretty good candidate for release -- we have (basically) cleared the entire list of blocking changes [8]! I'd like to ask everyone to give this candidate a try -- this is the last opportunity we have to fix any

Re: Apache: Big Data North America 2017 conference

Just a remainder that this is happening next week -- I hope to see many of your there! On Mon, Apr 24, 2017 at 7:18 AM, Aljoscha Krettek <aljos...@apache.org> wrote: > I’ll also be there. Looking forward to meeting all of you! > > Best, > Aljoscha > > On 24. Apr 2017, at

Re: Apache: Big Data North America 2017 conference

I think we'll plan as we go -- watch for updates here. Thursday would be the most likely day. On Tue, May 9, 2017 at 10:31 AM, Ashish <paliwalash...@gmail.com> wrote: > I will be there. > > Any hack hour planned yet or we plan on the go. > > On Mon, May 8, 2017 at 11:20

Re: Apache: Big Data North America 2017 conference

-of-a-Feather room, and figure out the logistics.) On Mon, May 15, 2017 at 10:10 AM, Davor Bonaci <da...@apache.org> wrote: > If you'd like to meet at the conference, I know many of us will be in the > Balmoral room immediately after the keynote finishes on Wednesday, around > 9:45 am or

Re: Website homepage visual refresh

I think it is great too -- since it is an obvious improvement, let's merge and iterate! On Tue, May 16, 2017 at 6:06 AM, Jean-Baptiste Onofré wrote: > Hi Jeremy, > > great job ! I like the new look'n feel. > > Thanks ! > Regards > JB > > > On 05/16/2017 07:44 AM, Jeremy

First stable release completed!

The first stable release is now complete! Release artifacts are available through various repositories, including dist.apache.org, Maven Central, and PyPI. The website is updated, and announcements are published. Apache Software Foundation press release:

Re: [VOTE] First stable release: release candidate #4

t; > > > >>> cause some tests to be skipped (but no failure). However, I > > don't > > > > > > >>> think it's worth cutting another release candidate for. > > > > > > >>> > > > > > > >>> Everything else is l

[RESULT] [VOTE] First stable release: release candidate #4

I'm happy to announce that we have unanimously approved this release. There are 14 approving votes, 6 of which are binding: * Ahmet Altay * Davor Bonaci * Robert Bradshaw * Lukasz Cwik * María García Herrero * Thomas Groh * Dan Halperin * Pei He * Chamikara Jayalath * Aljoscha Krettek * Jason

Apache Beam Meetup in Bay Area

. Location: Hortonworks HQ 5470 Great America Parkway, Santa Clara, CA, USA Agenda: 6:00 pm: Doors open 6:00 pm - 6:15 pm: Networking, Pizza and Drinks 6:15 pm - 6:30 pm: Introduction & Apache Beam release 2.0.0 - Rafael Coss and Davor Bonaci 6:30 pm - 7:15 pm: Using Apache Beam for Batch, Strea

Fwd: [Report] Eagle - June 2017

>From this month's Eagle report: "Community is working on Alert engine based Apache Beam, led by YHD.com. https://github.com/1haodian/eagle/tree/alertenginebeam; This could be an opportunity for someone in the Beam project to reach out, and help out with the cross-project integration. Any

Re: Reduced Availability from 17.6. - 24.6

To tag along on the same thread, I'm out through the Independence Day holiday. Back on 7/5. On Fri, Jun 16, 2017 at 10:03 PM, Aljoscha Krettek wrote: > Hi, > > I’ll be on vacation next week, just in case anyone is wondering why I’m > not responding. :-) > > Best, > Aljoscha

Re: [DISCUSS] Apache Beam 2.1.0 release next week ?

+1 On Thu, Jun 22, 2017 at 5:42 AM, Etienne Chauchot wrote: > Besides, there are some minor fixes/enhancements that lack in spark > > For info, bellow are the ones raised by nexmark test suite: > > https://issues.apache.org/jira/browse/BEAM-2499 > >

Re: Apache: Big Data North America 2017 conference

What an incredible conference this year. It was nice to meet many of you -- thanks everyone! On Wed, May 17, 2017 at 6:00 PM, Davor Bonaci <da...@apache.org> wrote: > Just a remainder that the Birds of a Feather sessions begins in 30 minutes > in the Windsor room. > > Aft

Re: Streaming Data Pipeline Support in Python

As a project, we don't have an official time-based roadmap. So far, the project went through the "standard" cycle: getting accepted into incubation, code donation, first release, graduation, and the first stable release last week. Going forward, I'll be looking into discussing and formalizing

Re: [Road map][R SDK]

> > Is there an "official" roadmap for 2017? > We don't have an official time-based roadmap. So far, the project went through the "standard" cycle: getting accepted into incubation, code donation, first release, graduation, and the first stable release last week. Going forward, I'll be looking

Re: New doc: Beam Runner Guide

Great work! Once comments are resolved in the document, can we move this to the Contribute section of the website? I think that would make it much more discoverable to everyone. On Mon, May 22, 2017 at 1:33 AM, Aljoscha Krettek wrote: > Cool, I’ll give this a read once I’m

Re: Python SDK: BigTableIO

(JIRA role added; reassigned.) On Thu, Jun 1, 2017 at 10:05 AM, Chamikara Jayalath wrote: > Thanks. I added some comments to the doc. > > Davor should be able to assign this JIRA to you. Also, Solomon who > implemented the Java BigTable connector might have more input

Report to the Board, June 2017 edition

We are expected to submit a project report to the ASF Board of Directors ahead of its next meeting. The report is due on Wednesday, 6/14. If interested, please take a look at the draft [1], and comment or contribute content, as appropriate. I'll submit the report sometime on Wednesday. Thanks!

Re: DataWorks Summit San Jose 2017

, Davor Bonaci <da...@apache.org> wrote: > Apache Beam will be featured at the DataWorks Summit / Hadoop Summit next > week in San Jose, CA [1]. > > Scheduled events: > * Realizing the promise of portable data processing with Apache Beam [2] > Time: Wednesday, 6/14, 11:

Re: Report to the Board, June 2017 edition

Thanks everyone; the report is now submitted. On Tue, Jun 13, 2017 at 7:47 AM, Davor Bonaci <da...@apache.org> wrote: > We are expected to submit a project report to the ASF Board of Directors > ahead of its next meeting. The report is due on Wednesday, 6/14. > > If inter

Re: First stable release: version designation?

gt; > > > 2.0.0. > > > > > > > > > > > > On Thu, May 4, 2017 at 12:25 PM, Lukasz Cwik > > > <lc...@google.com.invalid > > > > > > > > > > > wrote: > > > > > > > > > > > > &g

Re: Process for getting the first stable release out

is would reduce the > need for manual (and error-prone) cherry-picking. > > On Fri, May 5, 2017 at 5:21 PM, Davor Bonaci <da...@apache.org> wrote: > > The release branch is now created [1]. Anything for the first stable > > release should go into master as usual, and then get c

First stable release: Acceptance criteria

Based on the process previously discussed [1], I've seeded the acceptance criteria document [2]. Please consider contributing to this effort by: * proposing additional acceptance criteria, and/or * supporting criteria proposed by others, and/or * validating a criteria. Please note that

First stable release: release candidate #1

The release candidate #1 for the version 2.0.0 has been built. The complete staging area is available for review, which includes: * JIRA release notes [1], * the official Apache source release to be deployed to dist.apache.org [2], which is signed with the key with fingerprint 8F0D334F [3], * all

Re: Congratulations Davor!

t; > > >>>>> On May 4, 2017, at 7:08 AM, Amit Sela < > > > > > > > > amitsel...@gmail.com > > > > > > > > > > > > > > > > > > > > >> > wrote: > > > > > >

Re: Process for getting the first stable release out

ww.quora.com/Why-do-you-have-to-throw-out-the-first-pancake> > > will > > be not ready to serve customers. > > > > On Fri, May 5, 2017 at 11:40 AM, Kenneth Knowles <k...@google.com.invalid > > > > wrote: > > > > > On Thu, May 4, 2017 at 12:07 PM

Re: First stable release: version designation?

I slightly prefer1.0.0 for the *first* stable release, but fine > with > > > > 2.0.0. > > > > > > > > > > On Thu, May 4, 2017 at 12:25 PM, Lukasz Cwik > > <lc...@google.com.invalid > > > > > > > > > wrote: > > >

Re: Slack Invites

Off-topic: The most annoying thing (to me) is that Slack's auto-detection of self-invite bots is very sensitive to frequent invites of just one member. When this activates, we get blocked from inviting more people and we have to contact Slack support to unblock further invites. They resolve it

Process for getting the first stable release out

We've been working on the first stable release for a while now -- we've been tracking blocking issues [1], resolved many of them, organized a hackathon [2], and improved testing coverage in various areas. I think we are nearly done -- there are a few more blocking issues left in JIRA, and

Re: First stable release: version designation?

release process to make sure what is released is > > indeed stable. > > > > Normally people would have higher expectation on 2.0 release compared to > > 1.0 release. > > > > On Mon, Mar 6, 2017 at 6:34 PM, Davor Bonaci <da...@apache.org> wrote: > > > > > It

Re: Seeking help for running bash script in Maven

I don't believe this has anything to do with Maven. Maven isn't passing any arguments to the script, or anything similar. Script's location is figured out here: HERE="$(dirname $0)" and then used to like this: ARCHETYPE_ROOT="${HERE}/src/main/resources/archetype-resources" mkdir -p

DataWorks Summit San Jose 2017

Apache Beam will be featured at the DataWorks Summit / Hadoop Summit next week in San Jose, CA [1]. Scheduled events: * Realizing the promise of portable data processing with Apache Beam [2] Time: Wednesday, 6/14, 11:30 am Speaker: Davor Bonaci * Stateful processing of massive out-of-order

Report to the Board, September 2017 edition

We are expected to submit a project report to the ASF Board of Directors ahead of its next meeting. The report is due on Wednesday, 9/13. If interested, please take a look at the draft [1], and comment or contribute content, as appropriate. I'll submit the report sometime in the next 24 hours.

DataWorks Summit Sydney 2017

Apache Beam will be featured at the DataWorks Summit / Hadoop Summit next week in Sydney, Australia [1]. Scheduled events: * Realizing the promise of portable data processing with Apache Beam [2] Time: Thursday, 9/21, 3:10 pm Speaker: Davor Bonaci * Birds-of-a-feather: IoT, Streaming

Re: Report to the Board, September 2017 edition

Thanks everyone for a super quick turnaround! (The report is now submitted.) On Wed, Sep 13, 2017 at 10:45 AM, Davor Bonaci <da...@apache.org> wrote: > We are expected to submit a project report to the ASF Board of Directors > ahead of its next meeting. The report is due on Wed

Re: Euphoria Java 8 DSL - proposal

Hi David, As JB noted, merging of these two projects is a great idea. If fact, some of us have had those discussions in the past. Legally, nothing particular is strictly necessary as the code seem to already be Apache 2.0 licensed. We don't, however, want to be perceived as making hostile forks,

Re: Report to the Board, December 2017 edition

, 2017 at 1:58 PM, Griselda Cuevas <g...@google.com> wrote: >> >>> LGTM thanks for sharing. >>> >>> >>> >>> On 12 December 2017 at 20:54, Jean-Baptiste Onofré <j...@nanthrax.net> >>> wrote: >>> >>>> It

Report to the Board, December 2017 edition

We are expected to submit a project report to the ASF Board of Directors ahead of its next meeting. The report is due on Wednesday, 12/13. If interested, please take a look at the draft [1], and comment or contribute content, as appropriate. I'll submit the report sometime in the next 24 hours.

A personal update

My dear friends, As many of you have noticed, I’ve been visibly absent from the project for a little while. During this time, a great number of you kept reaching out, and for that I’m deeply humbled and grateful to each and every one of you. I needed some time for personal reflection, which led

Re: Apache Beam - jenkins question

nkins to access the credentials UI; once the >> credential is created in Jenkins it should be able to be set as an >> environment variable through the Jenkins job configuration (groovy files in >> $BEAM_ROOT/.test-infra/jenkins). Hope this helps. >> >> Jason >>

Re: Graal instead of docker?

This thread is extremely valuable. It poses hard questions. It strengthens good arguments. It teaches a way of thinking. It gives feedback. I want to thank Romain in particular for driving it, and everyone who has participated thus far. That being said, the exchange has crossed the line on behalf

Re: [VOTE] Go SDK

+1 (binding), with the following caveats: * [before closing the vote] Completion of IP clearance process, as we've been requested. It is easier to do it than having to argue why it is not necessary. * [at any time, possibly later] Figuring out the release mechanics. Great work; across the board!

Re: [VOTE] Go SDK

gt; On Tue, May 22, 2018 at 3:14 PM Robert Bradshaw <rober...@google.com> > wrote: > >> On Tue, May 22, 2018 at 2:42 PM Davor Bonaci <da...@apache.org> wrote: >> >> >>* Robert mentioned that "SGA should have probably already been >> file

Re: Missing copyright notices for shaded packages

t notice, this list of conditions and the following disclaimer in > the documentation and/or other materials provided with the distribution. > > (4) any proposed fix > > NOTICE file in the jar. > > I am not a lawyer, this is not legal advice. > > On Tue, May 22, 2018 at 2

  1   2   >