> In general, a 3+2+4 schedule was favored on the other thread, so I would > think using it would be good?
I know this is the favourite one on the other thread but I am thinking of making exception for 4.4 and adopt the preferred one from 4.5 so we have 4.4 target for Oct and 4.5 target is Q1 2027 WDYT? Sent from my iPhone > On 3 Jun 2026, at 17:04, Matthias J. Sax <[email protected]> wrote: > > Yes, I meant 2026 and 2027... somehow lagged a year :D > > > In general, a 3+2+4 schedule was favored on the other thread, so I would > think using it would be good? > > For KIP freeze date, seems we have many different proposals > - Jun/15 (Monday) > - July/1st (Wednesday) > - July/8th (Wednesday) > - July/15th (Wednesday) > - July/29 (Wednesday) > > Maybe we should pick something in the middle like July/1st or July/8th as a > compromise? > > > -Matthias > > On 6/3/26 8:29 AM, Chia-Ping Tsai wrote: >>>> Omnia Ibrahim <[email protected]> 於 2026年6月3日 晚上8:50 寫道： >>> >>> KIP freeze = 29th >>> July 2026 >>> Feature freeze = KIP freeze + 3 weeks == 19th Aug 2026 >>> Code freeze = Feature freeze + 3 weeks == 9th Sep 2026 >>> Release target = Code freeze + 4 weeks == 7th Oct 2026 >> +1 to this plan, allowing us to adopt the new schedule starting from 4.5.0 I >> just realize how rushed our previous releases were in this year. Our Kafka >> community is by far the most productive I’d say >> Best, >> Chia-Ping >
