Re: [DISCUSS] 1.2 release

We have a critical bug fix for Async high level API. The changes have been committed to master. Can we include that as part of 1.2? Thanks, Bharath On Mon, May 20, 2019 at 3:38 PM Jake Maes wrote

Re: [DISCUSS] 1.2 release

Ahh, perhaps I was mistaken. I must be thinking of a different ticket. Thanks for checking! On Mon, May 20, 2019 at 3:13 PM Boris S wrote: > @jmakes, Hmm, the git log actually shows a commit related to this JIRA, so > there is a code change associated with this ticket. And the ticket is > reso

Re: [DISCUSS] 1.2 release

From: Boris S Sent: Monday, May 20, 2019 3:12:59 PM To: dev@samza.apache.org Subject: Re: [DISCUSS] 1.2 release @jmakes, Hmm, the git log actually shows a commit related to this JIRA, so there is a code change associated with this ticket. And the ticket is resolved as FIXED. I can remove it the

Re: [DISCUSS] 1.2 release

@jmakes, Hmm, the git log actually shows a commit related to this JIRA, so there is a code change associated with this ticket. And the ticket is resolved as FIXED. I can remove it the tag from the jira, but I cannot remove it from the git log. On Mon, May 20, 2019 at 9:39 AM Jake Maes wrote: > I

Re: [DISCUSS] 1.2 release

+1 (non-binding) Thanks, On Mon, May 20, 2019 at 10:10 AM Xinyu Liu wrote: > +1 on the 1.2 release. It's time to get the newly added features out! > > Thanks, > Xinyu > > On Mon, May 20, 2019 at 9:39 AM Jake Maes wrote: > > > I don't think we did anything for "Making sendTo(table), sendTo(stre

Re: [DISCUSS] 1.2 release

+1 on the 1.2 release. It's time to get the newly added features out! Thanks, Xinyu On Mon, May 20, 2019 at 9:39 AM Jake Maes wrote: > I don't think we did anything for "Making sendTo(table), sendTo(stream) > non-terminal". The ticket was just closed as a "won't fix" IIRC. > > Nevertheless, I t

Re: [DISCUSS] 1.2 release

It seemed this PR has been committed https://github.com/apache/samza/pull/984 -Wei On 5/20/19, 9:39 AM, "Jake Maes" wrote: I don't think we did anything for "Making sendTo(table), sendTo(stream) non-terminal". The ticket was just closed as a "won't fix" IIRC. Nevertheless, I

Re: [DISCUSS] 1.2 release

I don't think we did anything for "Making sendTo(table), sendTo(stream) non-terminal". The ticket was just closed as a "won't fix" IIRC. Nevertheless, I think the Kafka 2.0 upgrade warrants a release by itself. Let's do it. On Fri, May 17, 2019 at 12:17 PM Boris S wrote: > Hi all, > > We have

[DISCUSS] 1.2 release

Hi all, We have added a number of major features and changes to master since 1.1 that warrants a new 1.2 release. Within LinkedIn, some of these features have already been tested as part of our test suites. We plan to continue our testing in coming week to validate the stability prior to release.