Hi Omnia and Chia-Ping Heads up that I cherry-picked a 1-line docs PR to 4.4 https://github.com/apache/kafka/pull/23256
Thanks, Bill On Mon, Aug 24, 2026 at 9:59 AM Mickael Maison <[email protected]> wrote: > Hi, > > I filed https://issues.apache.org/jira/browse/KAFKA-20979 > I don't think it's a regression but I think this is a potential data > loss even following a clean shutdown. > I opened a PR for the clean shutdown path: > https://github.com/apache/kafka/pull/23258 > > Thanks, > Mickael > > On Mon, Aug 24, 2026 at 12:58 PM Chia-Ping Tsai <[email protected]> > wrote: > > > > Hi Matthias > > > > I have reviewed https://github.com/apache/kafka/pull/23075 and left two > > small comments. > > > > The PR improves test coverage, so it would be great to backport it to 4.4 > > Thanks, > > Chia-Ping > > > > Matthias J. Sax <[email protected]> 於 2026年8月21日週五 上午7:23寫道： > > > > > I just approved https://github.com/apache/kafka/pull/23075 which adds > a > > > missing system test for 4.4.0 change. Can I cherry-pick it to 4.4 > branch > > > after merging to `trunk`? > > > > > > > > > -Matthias > > > > > > On 8/20/26 10:34 AM, Andrew Schofield wrote: > > > > Hi Chia-Ping, > > > > Thanks for digging into this. There are far too many tricky cases in > > > this area I feel. > > > > > > > > Thanks, > > > > Andrew > > > > > > > > On 2026/08/20 15:56:59 Chia-Ping Tsai wrote: > > > >> hi Andrew > > > >> > > > >> I just reviewed and backported > > > https://github.com/apache/kafka/pull/23014, but unfortunately I > noticed > > > another busy loop. I have created > > > https://issues.apache.org/jira/browse/KAFKA-20970, which is a blocker > > > too, to handle that busy loop. > > > >> > > > >> The ticket is already assigned to Ken, and I think we can tackle it > > > soon. > > > >> > > > >> Best, > > > >> Chia-Ping > > > >> > > > >> On 2026/08/20 11:28:56 Andrew Schofield wrote: > > > >>> Hi, > > > >>> I've just merged https://github.com/apache/kafka/pull/23014 into > > > trunk which address one of the 4.4 blockers. > > > >>> > > > >>> It should also be cherry-picked to 4.4. > > > >>> > > > >>> Thanks, > > > >>> Andrew > > > >>> > > > >>> On 2026/08/20 08:13:37 David Jacot wrote: > > > >>>> Hi Omnia, > > > >>>> > > > >>>> As agreed, I have merged > https://github.com/apache/kafka/pull/22969. > > > >>>> > > > >>>> Best, > > > >>>> David > > > >>>> > > > >>>> On Thu, Aug 20, 2026 at 9:35 AM Chia-Ping Tsai < > [email protected]> > > > wrote: > > > >>>>> > > > >>>>> hi all, > > > >>>>> > > > >>>>> I have merged the following commits to the 4.4 branch: > > > >>>>> > > > >>>>> > > > > https://github.com/apache/kafka/commit/0078945f4c31b3ad8ade4823d72ddec7482ead50 > : > > > consolidate tests to ensure the correct behavior logic > > > >>>>> > > > >>>>> > > > > https://github.com/apache/kafka/commit/b8e55ea90ee61e0592d68223a149920be918f76c > : > > > fix the docs missed from KIP-1301 > > > >>>>> > > > >>>>> Best, > > > >>>>> Chia-Ping > > > >>>>> > > > >>>>> On 2026/08/13 08:55:42 Omnia Ibrahim wrote: > > > >>>>>> Hi all > > > >>>>>> Code freeze for Apache Kafka 4.4.0 is now in effect. > > > >>>>>> From this point on, the 4.4 release branch will only accept > fixes > > > for blocker bugs. No new features or non‑critical changes should be > merged > > > into this branch until the 4.4.0 release is complete. > > > >>>>>> > > > >>>>>> Release plan: > > > > https://cwiki.apache.org/confluence/spaces/KAFKA/pages/429064575/Release+Plan+4.4.0 > > > >>>>>> > > > >>>>>> We’ll start the vote on the first RC soon, once we’ve scanned > all > > > Jira tickets to move out incomplete items and chased down the flaky > tests > > > we’ve found. > > > >>>>>> If you believe a change qualifies as a blocker or requires an > > > exception, please discuss it on this list and coordinate with > Chia‑Ping or > > > me before merging anything into the 4.4 branch. > > > >>>>>> > > > >>>>>> Thanks everyone for your contributions so far. > > > >>>>>> > > > >>>>>> Best, > > > >>>>>> Omnia > > > >>>>>> > > > >>>>>> > > > >>>> > > > >>> > > > >> > > > > > > >
