We recently identified the root cause of https://issues.apache.org/jira/browse/KAFKA-8649 and plan to do PR asap.
It seems to be a critical fix as it affect upgrading Kafka Streams applications. We would love to get a fix into 2.2.2 release. -Matthias On 9/23/19 10:45 PM, Matthias J. Sax wrote: > Just FYI: > > There was no further feedback about how to handle the regression in > 2.2.1 and hence, we consider the proposal accepted, what implies that we > can move forward with the 2.2.2 release. > > > -Matthias > > On 9/13/19 5:23 PM, Randall Hauch wrote: >> Thanks, Matthias. I'll get things ready locally but won't cut a release >> candidate until everyone is ready. >> >> On Fri, Sep 13, 2019 at 4:13 PM Matthias J. Sax <matth...@confluent.io> >> wrote: >> >>> Thanks Randall! >>> >>> Overall SGTM, however, we need to resolve the open question about the >>> 2.2.1 regression before we can release 2.2.2. >>> >>> I sent an email about this (subject `[DISCUSS] Streams-Broker >>> compatibility regression in 2.2.1 release`) couple of days ago. >>> >>> >>> -Matthias >>> >>> On 9/12/19 4:03 PM, Randall Hauch wrote: >>>> Hey everyone, >>>> >>>> I'd like to volunteer for the release manager of the 2.2.2 bug fix >>> release. >>>> Kafka 2.2.1 was >>>> released on June 3 and so far 25 issues have been fixed since then. Here >>> is >>>> a complete >>>> list: >>>> >>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20KAFKA%20AND%20status%20in%20(Resolved%2C%20Closed)%20AND%20fixVersion%20%3D%202.2.2 >>>> >>>> The release plan is documented here: >>>> https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+2.2.2 >>>> >>>> Thanks! >>>> >>>> Randall >>>> >>> >>> >> >
signature.asc
Description: OpenPGP digital signature
