Hello! Thanks Matthias and Chia-Ping for letting me know!
I have done one more audit on the remaining 9 JIRAs with a 4.2.0 tag in the release plan. The current blockers are KAFKA-19012, KAFKA-17862 and KAFKA-19999. What is the consensus on KAFKA-20003 - should I be treating it as a blocker? Matthias's bugfix is KAFKA-20002. I have requested a bit more information about the state of KAFKA-19851, KAFKA-19964, KAFKA-15370 and KAFKA-19891. They aren't currently marked as blockers, but there has been recent activity on all of them and I would like to understand whether we are aiming to include them in 4.2 or whether we are bumping them to 4.3. Let me know if I have missed something else! Best, Christo On Wed, 17 Dec 2025 at 16:18, Chia-Ping Tsai <[email protected]> wrote: > > hi > > there is another crucial issue regarding TV2 ( > https://issues.apache.org/jira/browse/KAFKA-19999) > > I hope we can ship it in 4.2.0 as well > > Best, > Chia-Ping > > Matthias J. Sax <[email protected]> 於 2025年12月17日週三 下午11:57寫道： > > > Hello, > > > > by chance, we found a critical bug in Kafka Streams yesterday: > > https://issues.apache.org/jira/browse/KAFKA-20002 -- PR is already up. > > It's a trivial fix. > > > > It's not a regression, as the issue was introduced with 4.0 release, and > > it's also not a blocker, and we are after code freeze. > > > > So want to highlight it. I would like to get it into 4.2.0 release if > > there are no objections. > > > > > > -Matthias > > > > On 11/28/25 7:14 AM, Christo Lolov wrote: > > > Heya! > > > > > > Added it, thanks for pointing it out. I have done one more audit and > > reached out to implementers for a couple of KIPs which should probably be > > moved to a subsequent release! > > > > > > Best, > > > Christo > > > > > >> On 26 Nov 2025, at 06:30, Herman K. Jakobsen <[email protected]> > > wrote: > > >> > > >> Looks like my previous mail unfortunately wasn't sent. However, could > > we > > >> include KIP-1146 - Anchored Punctuation? The feature is already > > implemented > > >> and merged to trunk. > > >> > > >> Thanks, > > >> > > >> Herman > > >> > > >>> On 2025/10/30 07:27:22 Christo Lolov 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 > > >>>>>>>> > > >>>>>>> > > >>> > > > >
