Re: 10/22/2018 Bi-Weekly OSS Heron Sync-up

2018-10-22 Thread Josh Fischer
1. I started conversations to get the podling report finished. 2. I pitched a proposal to make the Heron build hermetic. - Josh On Mon, Oct 22, 2018 at 9:03 PM Ning Wang wrote: > Agreed. Thanks. > > Yeah. It makes more send for everyone to send out updates individual. > > > > On Mon, Oct 22,

Heron OSS Sync meeting

2018-10-22 Thread Ning Wang
Hi, heron devs, The heron OSS sync meeting will be happening tomorrow at 2.00 pm PDT. Please use the following hangout link: https://hangouts.google.com/hangouts/_/streaml.io/oss-heron-sync?authuser=0 Please reply this email with your updates. Thanks! Here are my updates: - Added

Re: 10/22/2018 Bi-Weekly OSS Heron Sync-up

2018-10-22 Thread Dave Fisher
Hi - This is better in that it is on the list. Some principles of The Apache Way: 1. Vendor Neutral. 2. Merit is given to individuals. With that in mind for the next reports: A. There should not be a “Twitter side”. There is what contributors are doing. B. It helps to read on this mailing list

10/22/2018 Bi-Weekly OSS Heron Sync-up

2018-10-22 Thread Neng Lu
Hi All, It has been two weeks since our last sync and now is time to share our progress again. Let's share our works done for the last two weeks in this thread. And see if we need some online discussion for difficult problems. >From Twitter's side: 1. Ning Drafted the streamlet custom operator

Re: Podling Report Reminder - November 2018

2018-10-22 Thread Neng Lu
Any update on this Podling Report task? On Sat, Oct 20, 2018 at 10:46 AM Ning wrote: > Cool. Thanks! > > Sent from my iPhone > > > On Oct 20, 2018, at 10:13 AM, Josh Fischer wrote: > > > > I’ve pasted in the report from August. You can access where the template > > is to be input here —-> > >

Re: [VOTE] Heron Release 0.20.0-incubating Candidate 5

2018-10-22 Thread Neng Lu
@Jerry, any update on this issue? Should we open a separate thread in @dev to discuss this bazel issue? On Thu, Oct 18, 2018 at 11:32 PM Ning Wang wrote: > Bazel is often not backward compatible. Please use 0.14.1 > > I feel this might be the issue Sree had in this issue: >