> - KIP-909 This is still in progress. We've already addressed the DNS issues for the consumer and producer, but we're still working through some challenges with the Admin client. Also, we've decided to postpone the refactoring until after 4.3.0.
Best, Chia-Ping On 2026/03/24 15:00:54 Mickael Maison wrote: > Hi, > > Last week I gave a few extra days to the following KIPs: > - KIP-909 > - KIP-1035 > - KIP-1219 > - KIP-1285 > Can I have an update on their status? If we can't get them merged > really soon I'll have to move them to the next release. > > We're also tracking KIP-1274 which is just a new log line so we can > merge it till code freeze. > > Thanks, > Mickael > > On Fri, Mar 20, 2026 at 4:13 PM Mickael Maison <[email protected]> > wrote: > > > > Hi Chia-Ping, > > > > If that releases before code freeze, yes it should be fine. > > I'm one of the users "hounded by their security teams". > > > > Thanks, > > Mickael > > > > On Fri, Mar 20, 2026 at 4:11 PM Mickael Maison <[email protected]> > > wrote: > > > > > > Hi Bill, > > > > > > Yes that's fine. > > > > > > Thanks, > > > Mickael > > > > > > On Fri, Mar 20, 2026 at 3:55 PM Bill Bejeck <[email protected]> wrote: > > > > > > > > Hi Michael, > > > > > > > > For KIP-1035, the core implementation work got merged by the 18th, but > > > > the > > > > PR for the new metric still needs to be done. > > > > If we get it in by early next week, can we still cherry-pick this into > > > > 4.3? > > > > It should be a low-risk PR. > > > > > > > > Thanks, > > > > Bill > > > > > > > > On Fri, Mar 20, 2026 at 9:58 AM Chia-Ping Tsai <[email protected]> > > > > wrote: > > > > > > > > > hi Michael > > > > > > > > > > If Jetty 12.0.x is released before the 4.3 code freeze, I'll push > > > > > KAFKA-20344 to the 4.3 branch. This will be a huge relief for users > > > > > who are > > > > > currently being 'hounded' by their security teams. > > > > > > > > > > Best, > > > > > Chia-Ping > > > > > > > > > > On 2026/02/18 14:02:21 Mickael Maison wrote: > > > > > > Hi, > > > > > > > > > > > > Quick update to remind everyone that KIP freeze for 4.3.0 is next > > > > > > week. > > > > > > So if you want a KIP to be considered for 4.3.0 it must be accepted > > > > > > by > > > > > > the end of next week. > > > > > > > > > > > > Thanks, > > > > > > Mickael > > > > > > > > > > > > On Tue, Feb 10, 2026 at 5:23 PM Mickael Maison > > > > > > <[email protected]> > > > > > wrote: > > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > I've published a release plan for 4.3.0 on the wiki: > > > > > > > https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+4.3.0 > > > > > > > If I've missed a KIP, feel free to add it to the list. > > > > > > > > > > > > > > Let me know if you have any questions. > > > > > > > > > > > > > > Thanks, > > > > > > > Mickael > > > > > > > > > > > > > > > > > > > > > On Wed, Jan 28, 2026 at 5:04 AM Ismael Juma <[email protected]> > > > > > > > wrote: > > > > > > > > > > > > > > > > Thanks Mickael, +1 > > > > > > > > > > > > > > > > Ismael > > > > > > > > > > > > > > > > On Tue, Jan 27, 2026 at 5:15 AM Mickael Maison < > > > > > [email protected]> > > > > > > > > wrote: > > > > > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > > > > > I'd like to volunteer to be the release manager for the Apache > > > > > Kafka > > > > > > > > > 4.3.0 release. > > > > > > > > > > > > > > > > > > If there are no objections, I'll start building the release > > > > > > > > > plan. > > > > > > > > > 4.2.0 will now miss January, but I think we should still aim > > > > > > > > > at > > > > > having > > > > > > > > > 4.3.0 in May > > > > > > > > > > > > > > > > > > Thanks, > > > > > > > > > Mickael > > > > > > > > > > > > > > > > > > > > >
