Hello everyone, is there a date for this version release? I see that all issues have been released and that two RC version were built.
Thank you in advance. Antonio On 2025/10/09 16:19:14 "Matthias J. Sax" wrote: > Thanks Lianet! > > I was hoping for something earlier, but I agree that we need to give > enough time for the two blocker issues. > > > -Matthias > > > On 10/8/25 10:04 AM, Lianet M. wrote: > > Thanks for the updates Mickael and David! Both jiras in the plan as > > blockers. > > > > Lianet > > > > On Wed, Oct 8, 2025, 12:15 p.m. Mickael Maison <[email protected]> > > wrote: > > > >> Hi, > >> > >> Thanks Lianet for volunteering. > >> > >> Regarding the Connect issue, so far we've confirmed there's indeed a > >> regression introduced in 4.1.0 regarding plugin loading. > >> In the Jira [0] there is agreement on the expected behavior. I've > >> started working on a fix. > >> > >> I'll update you once things have progressed. > >> > >> Thanks, > >> Mickael > >> > >> 0: https://issues.apache.org/jira/browse/KAFKA-19758 > >> > >> On Wed, Oct 8, 2025 at 9:32 AM David Jacot <[email protected]> > >> wrote: > >>> > >>> Hi Lianet, > >>> > >>> Thanks for volunteering and the plan. > >>> > >>> I would like to get KAFKA-19760 in this release too. It is a nasty bug > >>> which impacts the reliability of the group/share coordinators. The PR is > >>> ready, it should be merged by the deadline. > >>> > >>> Best, > >>> David > >>> > >>> On Wed, Oct 8, 2025 at 3:58 AM Lianet M. <[email protected]> wrote: > >>> > >>>> Hello, > >>>> > >>>> Based on the previous discussion, here is a proposal of release plan > >> for > >>>> 4.1.1 > >>>> > >>>> https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+4.1.1 > >>>> > >>>> Aiming for code freeze in a week from now, mainly to allow time to > >>>> investigate the Connect issue Mickael shared ( > >>>> https://issues.apache.org/jira/browse/KAFKA-19758), but still be able > >> to > >>>> ship this release as soon as possible. Note that there is also an open > >>>> blocker but has a PR in review (I will follow-up with them) > >>>> > >>>> Let's wait to hear from Mickael, and we can adjust the target date if > >>>> needed. Let me know if you have any thoughts in the meantime. > >>>> > >>>> Thanks! > >>>> > >>>> Lianet > >>>> > >>>> > >>>> On Tue, Oct 7, 2025 at 1:09 PM Matthias J. Sax <[email protected]> > >> wrote: > >>>> > >>>>> Any idea how much time you will need Mickael? > >>>>> > >>>>> Personally, I would like to move fast, and delaying the release for > >> an > >>>>> uncertain amount of time seems not desirable. We will do a 4.1.2 > >> release > >>>>> for sure some time later. > >>>>> > >>>>> But I understand that it's a critical issue for Connect, so I agree > >> that > >>>>> it would be great to get into 4.1.1. (Or as a last resort, so a quick > >>>>> 4.1.2 after you figured out a fix, in case you need more time...) > >>>>> > >>>>> > >>>>> @Lianet: Thanks for volunteering to be the RM! Can you prepare a > >> release > >>>>> plan? > >>>>> > >>>>> > >>>>> -Matthias > >>>>> > >>>>> > >>>>> On 10/7/25 9:42 AM, Mickael Maison wrote: > >>>>>> Hi, > >>>>>> > >>>>>> If we do a 4.1.1 I'd like to include > >>>>>> https://issues.apache.org/jira/browse/KAFKA-19758. > >>>>>> I'm still investigating but it looks like KIP-891 broke plugin > >>>>>> isolation in Connect and thus workloads that worked with Connect > >> 4.0.0 > >>>>>> don't work anymore on 4.1.0. > >>>>>> > >>>>>> Thanks, > >>>>>> Mickael > >>>>>> > >>>>>> On Mon, Oct 6, 2025 at 3:54 PM Chia-Ping Tsai <[email protected]> > >>>>> wrote: > >>>>>>> > >>>>>>> +1 to release 4.1.1 ASAP > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> Lianet M. <[email protected]> 於 2025年10月6日 週一 下午9:33寫道： > >>>>>>> > >>>>>>>> Hello, > >>>>>>>> > >>>>>>>> Agree with the proposed 4.1.1 bug fix release to ship this asap. > >> If > >>>> we > >>>>> all > >>>>>>>> agree on the need for it, I would like to volunteer to be the > >> release > >>>>>>>> manager. > >>>>>>>> > >>>>>>>> Best, > >>>>>>>> Lianet > >>>>>>>> > >>>>>>>> On Fri, Oct 3, 2025 at 5:44 PM Matthias J. Sax <[email protected] > >>> > >>>>> wrote: > >>>>>>>> > >>>>>>>>> Hello, > >>>>>>>>> > >>>>>>>>> we now understand the recently reported memory leak bug in Kafka > >>>>> Streams > >>>>>>>>> 4.1.0, and have a PR to fix it. > >>>>>>>>> > >>>>>>>>> https://issues.apache.org/jira/browse/KAFKA-19748 > >>>>>>>>> > >>>>>>>>> I consider this bug severe, as we expect that it affects a large > >>>>> number > >>>>>>>>> of Kafka Streams user, makes Kafka Streams unusable, and there > >> is no > >>>>>>>>> workaround. > >>>>>>>>> > >>>>>>>>> So I would like to propose to start 4.1.1 bug-fix release > >>>> immediately, > >>>>>>>>> and also update the Kafka web page with a note that people > >> should be > >>>>>>>>> careful and maybe not even upgrade to Kafka Streams 4.1.0. > >>>>>>>>> > >>>>>>>>> Looking forward to your feedback. > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> -Matthias > >>>>>>>>> > >>>>>>>> > >>>>> > >>>>> > >>>> > >> > > > > [Logo] <https://www.vestigo.hr/> Antonio Soldo | Principal IT Architect, Framework Development & Technology Research M | +385 91 2680 283 Vestigo d.o.o., SR Njemačke 1b, 10010 Zagreb, Croatia<https://www.google.com/maps/place/Vestigo+d.o.o./@45.7615353,15.988841,17z/data=!3m1!4b1!4m5!3m4!1s0x4765d5ef1e6a34cb:0xa86811d16c97cb84!8m2!3d45.7615353!4d15.9910297> This e-mail message and any attachment may contain confidential and/or privileged information and is intended for use by the indicated addressee only. If you have received this message in error, please notify the sender immediately, destroy the original message and any attachment from your system. Unauthorized use, distribution, disclosure, reproduction, or alteration of this e-mail message is forbidden. Vestigo d.o.o. neither makes nor accepts legally binding statements via e-mail unless otherwise stated. Considering that internet communication is not secured, Vestigo d.o.o. is not responsible for the content of this message nor potential damage caused by its delivery or use.
