Thanks.
For KIP-1071 we are overall good. One PR opened just today against 4.4
to make some configs internal (as warmup task are not completed yet, and
thus these configs are unused): https://github.com/apache/kafka/pull/23100
Plus one minor follow up PR for KIP-1357 (related to 1071):
https://github.com/apache/kafka/pull/23092
We should merge both today or latest tomorrow.
-Matthias
On 8/11/26 9:33 AM, Chia-Ping Tsai wrote:
Hi Aditya,
Sorry for our limited review bandwidth. We have opened
https://github.com/apache/kafka/pull/23133 to revert it from 4.4.0.
We look forward to having your KIP included in 4.5.0!
Best,
Chia-Ping
Mickael Maison <[email protected]> 於 2026年8月12日 凌晨12:23 寫道：
Hi,
We're already way past feature freeze, so yes let's keep going with
the initial plan and the release.
I can see over a dozen KIPs marked as complete, there's already plenty
of content in 4.4.0.
Thanks,
Mickael
On Tue, Aug 11, 2026 at 6:14 PM Aditya Kousik <[email protected]> wrote:
Hi Chia,
Would it make sense to leave the public APIs in 4.4 for KIP-1306 but defer
https://issues.apache.org/jira/browse/KAFKA-20684 (adding the deprecated
annotation) to 4.5.0?
-Aditya
On Aug 11, 2026, at 09:03, Chia-Ping Tsai <[email protected]> wrote:
Hi Matthias,
I agree that we have run out of time and should stick to the strict rules of
our release plan.
I’ve confirmed that KIP-1332 is only partially completed. In addition, I will
revert KIP-1306 or at least remove its public APIs.
Matthias - would you mind checking the progress of KIP-1071?
Best,
Chia-Ping
Matthias J. Sax <[email protected]> 於 2026年8月11日 晚上11:16 寫道：
Thanks, I am ok with this.
But I am not sure I understand the overall sentiment. KIPs are supposed to be
completed by feature freeze, so if we want to give more time for KIPs to get
completed, we should have extended feature freeze deadling instead (and we
already effectively gave two more weeks, so we adding a third one now)
And we should use the time between feature freeze and code freeze to revert
changes of non-completed KIPs as necessary (ie, public API changes or similar
-- we opened two PR just today now that we have a 4.4 branch from our side)
Since feature freeze, actually only bug-fixes and minor KIP follow ups [of
completed KIPs] and new tests should get merged into AK 4.4 branch, to
stabilize the release branch before code freeze.
After code freeze, we should only accept blockers, not regular bug-fixes or
minor improvements any longer. Maybe there is some confusion about how the
deadlines are intended to work?
-Matthias
On 8/11/26 2:22 AM, Chia-Ping Tsai wrote:
hi Matthias
Given that there are still 7 incomplete KIPs and most of them are almost there,
I think it makes sense to extend the code freeze deadline by one week (to Aug
19th) to give the authors a bit more time.
However, after this extension, we should strictly freeze it. Reverting a KIP
from 4.4.0 is absolutely fine if the author does not have the bandwidth to
complete it by the new deadline.
I will review all tickets marked for 4.4.0 soon to ensure we don't miss any
critical bugs.
Best,
Chia-Ping
Matthias J. Sax <[email protected]> 於 2026年8月11日 下午2:41 寫道：
Does it stay as-is
