Thanks Matthias. It looks to me that we should fix all 4 issues. I would also suggest including the following trivial fix (we've seen this affect clusters in production):
https://github.com/apache/kafka/pull/6274 I'll create a JIRA for it. Ismael On Sat, Feb 16, 2019 at 12:51 PM Matthias J. Sax <matth...@confluent.io> wrote: > Hi, > > yesterday was code freeze. We have two open blocker tickets atm: > > - https://issues.apache.org/jira/browse/KAFKA-7920 > - https://issues.apache.org/jira/browse/KAFKA-7909 > > Both seems to be "on track" to get resolved soon. > > There is also two critical tickets: > > - https://issues.apache.org/jira/browse/KAFKA-7565 > - https://issues.apache.org/jira/browse/KAFKA-7672 > > If we can resolve them before the blockers are merged, I would be > willing to accept them. > > Additionally, there a 3 PRs that I plan to merge into 2.2 today because > we cannot cut an RC yet anyway (they are all approved but not merged yet > due to flaky tests that prevents us from getting green PR builds) > > Beside this, there are some flaky tests, that we might need to fix. The > nightly builds for 2.2 are not great so far: > > > https://builds.apache.org/blue/organizations/jenkins/kafka-2.2-jdk8/activity > > > I plan to cut the first RC as soon as the blockers are resolved. > > > Thanks a lot! > > -Matthias > > > On 2/14/19 12:33 AM, Matthias J. Sax wrote: > > Thanks for pointing out. It's was actually scheduled for Thursday 2/14. > > > > I will move it to Friday 2/15 (to not cut off a day from anybody...) > > > > > > -Matthias > > > > > > On 2/14/19 12:17 AM, James Cheng wrote: > >> Matthias, > >> > >> You said “Friday 2/14”, but 2/14 is this Thursday. > >> > >> -James > >> > >> Sent from my iPhone > >> > >>> On Feb 11, 2019, at 2:31 PM, Matthias J. Sax <matth...@confluent.io> > wrote: > >>> > >>> Hello, > >>> > >>> this is a short reminder, that feature freeze for AK 2.2 release is end > >>> of this week, Friday 2/14. > >>> > >>> Currently, there are two blocker issues > >>> > >>> - https://issues.apache.org/jira/browse/KAFKA-7909 > >>> - https://issues.apache.org/jira/browse/KAFKA-7481 > >>> > >>> and five critical issues > >>> > >>> - https://issues.apache.org/jira/browse/KAFKA-7915 > >>> - https://issues.apache.org/jira/browse/KAFKA-7565 > >>> - https://issues.apache.org/jira/browse/KAFKA-7556 > >>> - https://issues.apache.org/jira/browse/KAFKA-7304 > >>> - https://issues.apache.org/jira/browse/KAFKA-3955 > >>> > >>> marked with "fixed version" 2.2. Please let me know, if I missed any > >>> other blocker/critical issue that is relevant for 2.2 release. > >>> > >>> I will start to move out all other non-closed Jiras out of the release > >>> after code freeze and check again on the critical issues. > >>> > >>> After code freeze, only blocker issues can be merged to 2.2 branch. > >>> > >>> > >>> Thanks a lot! > >>> > >>> -Matthias > >>> > >>>> On 1/19/19 11:09 AM, Matthias J. Sax wrote: > >>>> Thanks you all! > >>>> > >>>> Added 291, 379, 389, and 420 for tracking. > >>>> > >>>> > >>>> -Matthias > >>>> > >>>> > >>>>> On 1/19/19 6:32 AM, Dongjin Lee wrote: > >>>>> Hi Matthias, > >>>>> > >>>>> Thank you for taking the lead. KIP-389[^1] was accepted last > week[^2], so > >>>>> it seems like to be included. > >>>>> > >>>>> Thanks, > >>>>> Dongjin > >>>>> > >>>>> [^1]: > >>>>> > https://cwiki.apache.org/confluence/display/KAFKA/KIP-389%3A+Introduce+a+configurable+consumer+group+size+limit > >>>>> [^2]: > >>>>> > https://lists.apache.org/thread.html/53b84cc35c93eddbc67c8d0dd86aedb93050e45016dfe0fc7b82caaa@%3Cdev.kafka.apache.org%3E > >>>>> > >>>>>> On Sat, Jan 19, 2019 at 9:04 PM Alex D <a.a.dunayev...@gmail.com> > wrote: > >>>>>> > >>>>>> KIP-379? > >>>>>> > >>>>>>> On Fri, 18 Jan 2019, 22:33 Matthias J. Sax <matth...@confluent.io > wrote: > >>>>>>> > >>>>>>> Just a quick update on the release. > >>>>>>> > >>>>>>> > >>>>>>> We have 22 KIP atm: > >>>>>>> > >>>>>>> 81, 207, 258, 289, 313, 328, 331, 339, 341, 351, 359, 361, 367, > 368, > >>>>>>> 371, 376, 377, 380, 386, 393, 394, 414 > >>>>>>> > >>>>>>> Let me know if I missed any KIP that is targeted for 2.2 release. > >>>>>>> > >>>>>>> 21 of those KIPs are accepted, and the vote for the last one is > open and > >>>>>>> can be closed on time. > >>>>>>> > >>>>>>> The KIP deadline is Jan 24, so if any late KIPs are coming in, the > vote > >>>>>>> must be started latest next Monday Jan 21, to be open for at least > 72h > >>>>>>> and to meet the deadline. > >>>>>>> > >>>>>>> Also keep the feature freeze deadline in mind (31 Jan). > >>>>>>> > >>>>>>> > >>>>>>> Besides this, there are 91 open tickets and 41 ticket in progress. > I > >>>>>>> will start to go through those tickets soon to see what will make > it > >>>>>>> into 2.2 and what we need to defer. If you have any tickets > assigned to > >>>>>>> yourself that are target for 2.2 and you know you cannot make it, I > >>>>>>> would appreciate if you could update those ticket yourself to help > >>>>>>> streamlining the release process. Thanks a lot for you support! > >>>>>>> > >>>>>>> > >>>>>>> -Matthias > >>>>>>> > >>>>>>> > >>>>>>>> On 1/8/19 7:27 PM, Ismael Juma wrote: > >>>>>>>> Thanks for volunteering Matthias! The plan sounds good to me. > >>>>>>>> > >>>>>>>> Ismael > >>>>>>>> > >>>>>>>>> On Tue, Jan 8, 2019, 1:07 PM Matthias J. Sax < > matth...@confluent.io > >>>>>>>> wrote: > >>>>>>>> > >>>>>>>>> Hi all, > >>>>>>>>> > >>>>>>>>> I would like to propose a release plan (with me being release > manager) > >>>>>>>>> for the next time-based feature release 2.2.0 in February. > >>>>>>>>> > >>>>>>>>> The recent Kafka release history can be found at > >>>>>>>>> > https://cwiki.apache.org/confluence/display/KAFKA/Future+release+plan > >>>>>> . > >>>>>>>>> The release plan (with open issues and planned KIPs) for 2.2.0 > can be > >>>>>>>>> found at > >>>>>> > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=100827512 > >>>>>>>>> . > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> Here are the suggested dates for Apache Kafka 2.2.0 release: > >>>>>>>>> > >>>>>>>>> 1) KIP Freeze: Jan 24, 2019. > >>>>>>>>> > >>>>>>>>> A KIP must be accepted by this date in order to be considered > for this > >>>>>>>>> release) > >>>>>>>>> > >>>>>>>>> 2) Feature Freeze: Jan 31, 2019 > >>>>>>>>> > >>>>>>>>> Major features merged & working on stabilization, minor features > have > >>>>>>>>> PR, release branch cut; anything not in this state will be > >>>>>> automatically > >>>>>>>>> moved to the next release in JIRA. > >>>>>>>>> > >>>>>>>>> 3) Code Freeze: Feb 14, 2019 > >>>>>>>>> > >>>>>>>>> The KIP and feature freeze date is about 2-3 weeks from now. > Please > >>>>>> plan > >>>>>>>>> accordingly for the features you want push into Apache Kafka > 2.2.0 > >>>>>>> release. > >>>>>>>>> > >>>>>>>>> 4) Release Date: Feb 28, 2019 (tentative) > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> -Matthias > >>> > > > >
