It seemed this PR has been committed
https://github.com/apache/samza/pull/984

-Wei


On 5/20/19, 9:39 AM, "Jake Maes" <jma...@apache.org> 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 <bor...@gmail.com> 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
    >
    

Reply via email to