hi Christo Could we include KIP-1196 and KIP-1231 in the 4.2 release? Their implementations are simple, so I believe they can be completed in time for the feature freeze.
Best, Chia-Ping On 2025/11/03 09:39:48 Christo Lolov wrote: > Heya Justine, > > Sure, I will include it in the release plan! Let me know if you encounter > issues with implementation or reviews! > > Best, > Christo > > > On 30 Oct 2025, at 16:27, Justine Olshan <[email protected]> > > wrote: > > > > Hey Christo > > I was wondering if we could include KIP-1228 in the 4.2 release. We have > > the required votes -- we just didn't officially close the vote yet. > > I think we should also be able to implement it in time for the feature > > freeze. What do you think? > > > > Thanks, > > Justine > > > >> On Thu, Oct 30, 2025 at 12:28 AM Christo Lolov <[email protected]> > >> wrote: > >> > >> Hello! > >> > >> We have now passed the KIP freeze date for 4.2.0. The next goal is the > >> feature freeze on the 19th of November! > >> > >> Feel free to reachout on this thread if your changes are not getting > >> traction to meet that date! > >> > >> Best, > >> Christo > >> > >>> On Wed, 22 Oct 2025 at 11:16, Christo Lolov <[email protected]> > >>> wrote: > >>> > >>> Hello! > >>> > >>> This is to bump the 4.2.0 thread to the top of the mailing list! > >>> > >>> The KIP freeze date is 1 week from today on the 29th of October. > >>> Please ensure that you have the required number of binding votes for > >>> your KIP by that date if you would like it included in 4.2.0. > >>> > >>> Best, > >>> Christo > >>> > >>> On Thu, 2 Oct 2025 at 15:08, Mickael Maison <[email protected]> > >> wrote: > >>>> > >>>> Hi, > >>>> > >>>> I think moving code freeze to December 10 makes sense. > >>>> Many people will be off the last 2 weeks of December, so it's best to > >>>> not have deadlines then. > >>>> > >>>> Thanks, > >>>> Mickael > >>>> > >>>> On Thu, Oct 2, 2025 at 3:49 PM Christo Lolov <[email protected]> > >> wrote: > >>>>> > >>>>> Hello! > >>>>> > >>>>> Thanks for the review! > >>>>> > >>>>> I am okay with pulling all dates by 2 weeks earlier in time (barring > >> the > >>>>> 7th of January one). If there are no objections to the new dates I > >> will > >>>>> update them in the plan tomorrow! > >>>>> > >>>>> Best, > >>>>> Christo > >>>>> > >>>>> On Thu, 2 Oct 2025 at 07:14, Ismael Juma <[email protected]> wrote: > >>>>> > >>>>>> Hi Christo, > >>>>>> > >>>>>> Thanks for managing the release and for the proposed release plan. > >>>>>> > >>>>>> Given our desire to ship every 4 months, I think the proposed > >> dates should > >>>>>> be shifted a bit. The original plan was for 4.1 to ship in mid > >> July and for > >>>>>> 4.2 to ship in mid November. The former eventually shipped on > >> September 2nd > >>>>>> and with the current plan would probably result in 4.2 shipping in > >> late > >>>>>> January/early February. Given where we are, I would suggest > >> something like: > >>>>>> > >>>>>> KIP Freeze: October 29 (Wednesday) > >>>>>> Feature Freeze: November 19 (Wednesday) > >>>>>> Code Freeze: December 10 (Wednesday) > >>>>>> At least four weeks of stabilization will follow Code Freeze > >> (taking > >>>>>> holidays into account), meaning we expect to release no earlier > >> than > >>>>>> January 7 2026. > >>>>>> > >>>>>> Ideally, we'd get RC0 out before the holiday break and then > >> complete the > >>>>>> release by early/mid January. > >>>>>> > >>>>>> Thoughts? > >>>>>> > >>>>>> Ismael > >>>>>> > >>>>>> On Tue, Sep 30, 2025 at 6:09 AM Christo Lolov < > >> [email protected]> > >>>>>> wrote: > >>>>>> > >>>>>>> Hello! > >>>>>>> > >>>>>>> I would like to volunteer to be the release manager for the > >> Apache Kafka > >>>>>>> 4.2.0 release. > >>>>>>> > >>>>>>> If no one has any objections, you can find a proposed release > >> plan at > >>>>>>> > >> https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+4.2.0. > >>>>>>> > >>>>>>> Thanks, > >>>>>>> Christo > >>>>>>> > >>>>>> > >> >
