Hi Divij, Thanks for the explanation, makes sense.
Hi Luke, thanks you! It would be awesome to see 3.5.2 out. Best, Levani > On 12. Oct 2023, at 12:39, Luke Chen <show...@gmail.com> wrote: > > Hi Levani and Divij, > > I can work on the 3.5.2 release. > I'll start a new thread for volunteering it maybe next week. > > Thanks. > Luke > > On Thu, Oct 12, 2023 at 5:07 PM Divij Vaidya <divijvaidy...@gmail.com> > wrote: > >> Hello Levani >> >> From a process perspective, there is no fixed schedule for bug fix >> releases. If we have a volunteer for release manager (must be a committer), >> they can start with the process of bug fix release (with the approval of >> PMC). >> >> My personal opinion is that it's too early to start 3.6.1 and we should >> wait at least 1 months to hear feedback on 3.6.0. We need to make a careful >> balance between getting the critical fixes in the hands of users as soon >> as possible vs. spending community effort towards releases (the effort that >> could be used to make Kafka better, feature-wise & operational >> stability-wise, otherwise). >> >> For 3.5.2, I think there are sufficient pending (including some CVE fixes) >> to start a bug fix release. We just need a volunteer for the release >> manager. >> >> -- >> Divij Vaidya >> >> >> >> On Thu, Oct 12, 2023 at 9:57 AM Levani Kokhreidze <levani.co...@gmail.com> >> wrote: >> >>> Hello, >>> >>> KAFKA-15571 [1] was merged and backported to the 3.5 and 3.6 branches. >> Bug >>> fixes the feature that was added in 3.5. Considering the feature doesn't >>> work as expected without a fix, I would like to know if it's reasonable >> to >>> start the 3.5.2 release. Of course, releasing such a massive project like >>> Kafka is not a trivial task, and I am looking for the community's input >> on >>> this if it's reasonable to start the 3.5.2 release process. >>> >>> Best, >>> Levani >>> >>> [1] - https://issues.apache.org/jira/browse/KAFKA-15571 >>
