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/18 04:15:32 Chia-Ping Tsai wrote:
> > I'd like to cherry-pick this to 4.4, given it's a one-line change seems low
> > risk.
> 
> I have reviewed that change and cherry-picked it to 4.4
> 
> Thanks,
> Chia-Ping
> 
> On 2026/08/17 17:17:44 Bill Bejeck wrote:
> > Hi Omina and Chia-Ping
> > 
> > I have a minor PR (one line change)
> > https://github.com/apache/kafka/pull/23182 that I'll get merged soon.
> > I'd like to cherry-pick this to 4.4, given it's a one-line change seems low
> > risk.
> > 
> > What do you think?
> > 
> > Thanks!
> > Bill
> > 
> > On Fri, Aug 14, 2026 at 5:02 PM <[email protected]> wrote:
> > 
> > > Hi Bill
> > > Thanks for updating us, yes please go ahead and cherry-pick it to 4.4
> > > Sent from my iPhone
> > >
> > > > On 14 Aug 2026, at 21:59, Bill Bejeck <[email protected]> wrote:
> > > >
> > > > Hi Omnia and Chia-Ping
> > > >
> > > > I have a minor docs PR https://github.com/apache/kafka/pull/23131 that I
> > > > just merged into trunk.
> > > > Ok to cherry-pick to 4.4?
> > > >
> > > > Thanks,
> > > > Bill
> > > >
> > > >> On Fri, Aug 14, 2026 at 4:48 PM Bill Bejeck <[email protected]> wrote:
> > > >>
> > > >> Hi Omnia and Chia-Ping,
> > > >>
> > > >> I've merged my blocker fix to trunk and cherry-picked to 4.4
> > > >> I initially raised the issue here
> > > >> <https://lists.apache.org/thread/sktbl653wbxhbhbfsgh54bwd3jgspqy4>.
> > > >>
> > > >> Thanks,
> > > >> Bill
> > > >>
> > > >>
> > > >>> On Fri, Aug 14, 2026 at 1:38 PM <[email protected]> wrote:
> > > >>>
> > > >>> Matthias I had a look all seems very small and no risk please go ahead
> > > >>> and cherry pick them to 4.4
> > > >>> Sent from my iPhone
> > > >>>
> > > >>>> On 14 Aug 2026, at 16:50, Matthias J. Sax <[email protected]> wrote:
> > > >>>>
> > > >>>> I have three smaller merged PRs I would like to cherry-pick to 4.4
> > > >>> branch. If we don't cherry-pick now, I would need to cycle back to
> > > >>> cherry-pick for 4.4.1 release what seems unnecessary bookkeeping
> > > overhead.
> > > >>>>
> > > >>>> Given that we are waiting for some blockers to get resolved anyway,
> > > >>> there should be zero impact on the release; all three are low risk of
> > > >>> course.
> > > >>>>
> > > >>>> Please let me know:
> > > >>>> - https://github.com/apache/kafka/pull/23080
> > > >>>> - https://github.com/apache/kafka/pull/23002
> > > >>>> - https://github.com/apache/kafka/pull/23143
> > > >>>>
> > > >>>>
> > > >>>>
> > > >>>> -Matthias
> > > >>>>
> > > >>>>> On 8/12/26 9:53 AM, José Armando García Sancio via dev wrote:
> > > >>>>> Hi Chia-Ping,
> > > >>>>> That decision sounds good to me. I marked it as fixed in 4.5.0 and
> > > >>>>> will not cherry pick it to the 4.4 branch.
> > > >>>>> Thanks!
> > > >>>>>> On Wed, Aug 12, 2026 at 12:36 PM Chia-Ping Tsai <[email protected]
> > > >
> > > >>> wrote:
> > > >>>>>>
> > > >>>>>> hi José
> > > >>>>>>
> > > >>>>>> Actually, we did NOT extend the code freeze :)
> > > >>>>>>
> > > >>>>>> The only commits we are pushing to the 4.4 branch right now are to
> > > >>> revert incomplete KIPs.
> > > >>>>>>
> > > >>>>>> KAFKA-16517 is a kind of performance optimization, right? If so, it
> > > >>> doesn't seem necessary for 4.4.0.
> > > >>>>>>
> > > >>>>>> Please correct me if I am wrong.
> > > >>>>>>
> > > >>>>>> Best,
> > > >>>>>> Chia-Ping
> > > >>>>>>
> > > >>>>>> José Armando García Sancio via dev <[email protected]> 於
> > > >>> 2026年8月13日週四 上午12:28寫道:
> > > >>>>>>>
> > > >>>>>>> Hi Chia-Ping,
> > > >>>>>>>
> > > >>>>>>> Thanks for volunteering to release 4.4. Since we extended the code
> > > >>>>>>> freeze to Aug 19th, I would like to include KAFKA-16517 in the 4.4
> > > >>>>>>> release.
> > > >>>>>>>
> > > >>>>>>> Do you agree? Can I cherry pick the commit
> > > >>>>>>> (https://github.com/apache/kafka/pull/22805) to the 4.4 branch?
> > > >>>>>>>
> > > >>>>>>> Thanks,
> > > >>>>>>> -José
> > > >>>>
> > > >>>
> > > >>
> > >
> > 
> 

Reply via email to