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: 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

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

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

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: 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: 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: 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

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: 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

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: 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: 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: [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: [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: [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/ *

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: 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] 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: [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: 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: 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: [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: 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]

<    1   2