Re: [DISCUSS] 1.2 release

[Bharath Kumara Subramanian]

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:

> 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
> > 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 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 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.
> > > >
> > > > We wanted to kick off the discussion in the open source forum to keep
> > > > the momentum flowing.
> > > > Here is a selected list of features that are part of the new release
> > > >
> > > >   Kafka 2.0 upgrade
> > > >
> > > >   Couchbase support for Samza Table API
> > > >   Making sendTo(table), sendTo(stream) non-terminal
> > > >
> > > > We have also worked on the following upgrades and bugfixes.
> > > > You can find a concrete list of the features, bug-fixes, upgrades
> > > > herehttps://
> > > >
> > >
> >
> issues.apache.org/jira/issues/?jql=project%20%3D%20%22SAMZA%22%20and%20fixVersion%20in%20(1.2)
> > > >
> > > >
> > > > Some of these Jiras are not marked as fixed (but they are marked as
> > > > committed in the git log). Please close the Jiras is they are fixed.
> > > >
> > > > Here is my proposal on our release schedule and timelines.
> > > >1. Cut the 1.2 release branch.
> > > >2. Target a release vote on the week of May 20, 2019
> > > >
> > > >
> > > > Thanks
> > > > Boris
> > > >
> > >
> >
>

Re: [DISCUSS] 1.2 release

[Jake Maes]

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
> 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 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 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.
> > >
> > > We wanted to kick off the discussion in the open source forum to keep
> > > the momentum flowing.
> > > Here is a selected list of features that are part of the new release
> > >
> > >   Kafka 2.0 upgrade
> > >
> > >   Couchbase support for Samza Table API
> > >   Making sendTo(table), sendTo(stream) non-terminal
> > >
> > > We have also worked on the following upgrades and bugfixes.
> > > You can find a concrete list of the features, bug-fixes, upgrades
> > > herehttps://
> > >
> >
> issues.apache.org/jira/issues/?jql=project%20%3D%20%22SAMZA%22%20and%20fixVersion%20in%20(1.2)
> > >
> > >
> > > Some of these Jiras are not marked as fixed (but they are marked as
> > > committed in the git log). Please close the Jiras is they are fixed.
> > >
> > > Here is my proposal on our release schedule and timelines.
> > >1. Cut the 1.2 release branch.
> > >2. Target a release vote on the week of May 20, 2019
> > >
> > >
> > > Thanks
> > > Boris
> > >
> >
>

Re: [DISCUSS] 1.2 release

[Sanil Jain]

@Jake Maes<mailto:jm...@linkedin.com>@Wei Song<mailto:ws...@linkedin.com> I 
worked on Samza-2116 and details can be found here: 
https://issues.apache.org/jira/browse/SAMZA-2116, the corresponding PR is 
checked-in as Wei pointed out!


Thanks

Sanil


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 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 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 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.
> >
> > We wanted to kick off the discussion in the open source forum to keep
> > the momentum flowing.
> > Here is a selected list of features that are part of the new release
> >
> >   Kafka 2.0 upgrade
> >
> >   Couchbase support for Samza Table API
> >   Making sendTo(table), sendTo(stream) non-terminal
> >
> > We have also worked on the following upgrades and bugfixes.
> > You can find a concrete list of the features, bug-fixes, upgrades
> > herehttps://
> >
> issues.apache.org/jira/issues/?jql=project%20%3D%20%22SAMZA%22%20and%20fixVersion%20in%20(1.2)
> >
> >
> > Some of these Jiras are not marked as fixed (but they are marked as
> > committed in the git log). Please close the Jiras is they are fixed.
> >
> > Here is my proposal on our release schedule and timelines.
> >1. Cut the 1.2 release branch.
> >2. Target a release vote on the week of May 20, 2019
> >
> >
> > Thanks
> > Boris
> >
>

Re: [DISCUSS] 1.2 release

[Boris S]

@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 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 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.
> >
> > We wanted to kick off the discussion in the open source forum to keep
> > the momentum flowing.
> > Here is a selected list of features that are part of the new release
> >
> >   Kafka 2.0 upgrade
> >
> >   Couchbase support for Samza Table API
> >   Making sendTo(table), sendTo(stream) non-terminal
> >
> > We have also worked on the following upgrades and bugfixes.
> > You can find a concrete list of the features, bug-fixes, upgrades
> > herehttps://
> >
> issues.apache.org/jira/issues/?jql=project%20%3D%20%22SAMZA%22%20and%20fixVersion%20in%20(1.2)
> >
> >
> > Some of these Jiras are not marked as fixed (but they are marked as
> > committed in the git log). Please close the Jiras is they are fixed.
> >
> > Here is my proposal on our release schedule and timelines.
> >1. Cut the 1.2 release branch.
> >2. Target a release vote on the week of May 20, 2019
> >
> >
> > Thanks
> > Boris
> >
>

Re: [DISCUSS] 1.2 release

[santhosh venkat]

+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(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 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.
> > >
> > > We wanted to kick off the discussion in the open source forum to keep
> > > the momentum flowing.
> > > Here is a selected list of features that are part of the new release
> > >
> > >   Kafka 2.0 upgrade
> > >
> > >   Couchbase support for Samza Table API
> > >   Making sendTo(table), sendTo(stream) non-terminal
> > >
> > > We have also worked on the following upgrades and bugfixes.
> > > You can find a concrete list of the features, bug-fixes, upgrades
> > > herehttps://
> > >
> >
> issues.apache.org/jira/issues/?jql=project%20%3D%20%22SAMZA%22%20and%20fixVersion%20in%20(1.2)
> > >
> > >
> > > Some of these Jiras are not marked as fixed (but they are marked as
> > > committed in the git log). Please close the Jiras is they are fixed.
> > >
> > > Here is my proposal on our release schedule and timelines.
> > >1. Cut the 1.2 release branch.
> > >2. Target a release vote on the week of May 20, 2019
> > >
> > >
> > > Thanks
> > > Boris
> > >
> >
>

Re: [DISCUSS] 1.2 release

[Xinyu Liu]

+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 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 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.
> >
> > We wanted to kick off the discussion in the open source forum to keep
> > the momentum flowing.
> > Here is a selected list of features that are part of the new release
> >
> >   Kafka 2.0 upgrade
> >
> >   Couchbase support for Samza Table API
> >   Making sendTo(table), sendTo(stream) non-terminal
> >
> > We have also worked on the following upgrades and bugfixes.
> > You can find a concrete list of the features, bug-fixes, upgrades
> > herehttps://
> >
> issues.apache.org/jira/issues/?jql=project%20%3D%20%22SAMZA%22%20and%20fixVersion%20in%20(1.2)
> >
> >
> > Some of these Jiras are not marked as fixed (but they are marked as
> > committed in the git log). Please close the Jiras is they are fixed.
> >
> > Here is my proposal on our release schedule and timelines.
> >1. Cut the 1.2 release branch.
> >2. Target a release vote on the week of May 20, 2019
> >
> >
> > Thanks
> > Boris
> >
>

Re: [DISCUSS] 1.2 release

[Wei Song]

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 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 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.
>
> We wanted to kick off the discussion in the open source forum to keep
> the momentum flowing.
> Here is a selected list of features that are part of the new release
>
>   Kafka 2.0 upgrade
>
>   Couchbase support for Samza Table API
>   Making sendTo(table), sendTo(stream) non-terminal
>
> We have also worked on the following upgrades and bugfixes.
> You can find a concrete list of the features, bug-fixes, upgrades
> herehttps://
> 
issues.apache.org/jira/issues/?jql=project%20%3D%20%22SAMZA%22%20and%20fixVersion%20in%20(1.2)
>
>
> Some of these Jiras are not marked as fixed (but they are marked as
> committed in the git log). Please close the Jiras is they are fixed.
>
> Here is my proposal on our release schedule and timelines.
>1. Cut the 1.2 release branch.
>2. Target a release vote on the week of May 20, 2019
>
>
> Thanks
> Boris
>

Re: [DISCUSS] 1.2 release

[Jake Maes]

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 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.
>
> We wanted to kick off the discussion in the open source forum to keep
> the momentum flowing.
> Here is a selected list of features that are part of the new release
>
>   Kafka 2.0 upgrade
>
>   Couchbase support for Samza Table API
>   Making sendTo(table), sendTo(stream) non-terminal
>
> We have also worked on the following upgrades and bugfixes.
> You can find a concrete list of the features, bug-fixes, upgrades
> herehttps://
> issues.apache.org/jira/issues/?jql=project%20%3D%20%22SAMZA%22%20and%20fixVersion%20in%20(1.2)
>
>
> Some of these Jiras are not marked as fixed (but they are marked as
> committed in the git log). Please close the Jiras is they are fixed.
>
> Here is my proposal on our release schedule and timelines.
>1. Cut the 1.2 release branch.
>2. Target a release vote on the week of May 20, 2019
>
>
> Thanks
> Boris
>