Hi Divij,

1. I will take a look
2. I am not sure what we did for earlier releases. But we can update the
dependencies if any CVE exists
3. Thanks for looking into backports.
4. Sure, we can ping the committers  where PR is available
5. I have not looked at 3.7 bugs. I will also take a look.

Thanks,
Manikumar

On Thu, Mar 14, 2024 at 2:09 PM Divij Vaidya <divijvaidy...@gmail.com>
wrote:

> Hi Manikumar,
>
> 1. Can you please take a look at
> https://github.com/apache/kafka/pull/15490
> which is a bug fix specific to the 3.6.x branch?
> 2. Should we do a one-time update of all dependencies in 3.6.x branch
> before releasing 3.6.2?
> 3. We fixed quite a lot of flaky tests in 3.7.x. I will see if any
> backporting is needed to make the release qualification easier.
> 4. There are a large number of bugs reported as impacting 3.6.1 [1] Some of
> them have attached PRs and pending review. Maybe we can request all
> committers to take a look at the ones which have a PR attached and see if
> we can close them in the next few days before 3.6.2. Note that this will be
> on a best-effort basis and won't block release of 3.6.2.
> 5. Have you looked at the JIRA marked as "bugs" in 3.7 and triaged whether
> something needs to be backported? Usually it is the responsibility of the
> reviewer but I have observed that sometimes we forget to backport important
> onces as well. I can help with this one early next week.
>
> [1]
>
> https://issues.apache.org/jira/browse/KAFKA-16222?jql=project%20%3D%20KAFKA%20AND%20issuetype%20%3D%20Bug%20AND%20resolution%20%3D%20Unresolved%20AND%20affectedVersion%20%3D%203.6.1%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC
>
>
> --
> Divij Vaidya
>
>
>
> On Thu, Mar 14, 2024 at 7:55 AM Manikumar <manikumar.re...@gmail.com>
> wrote:
>
> > Hi all,
> >
> > Here is the release plan for 3.6.2:
> > https://cwiki.apache.org/confluence/display/KAFKA/Release+plan+3.6.2
> >
> > Currently there is one open non-blocker issue. I plan to generate the
> first
> > release candidate
> > once the issue is resolved and no other issues are raised in the
> meantime.
> >
> > Thanks,
> > Manikumar
> >
> > On Thu, Mar 14, 2024 at 6:24 AM Satish Duggana <satish.dugg...@gmail.com
> >
> > wrote:
> >
> > > +1, Thanks Mani for volunteering.
> > >
> > > On Thu, 14 Mar 2024 at 06:01, Luke Chen <show...@gmail.com> wrote:
> > > >
> > > > +1, Thanks Manikumar!
> > > >
> > > > On Thu, Mar 14, 2024 at 3:40 AM Bruno Cadonna <cado...@apache.org>
> > > wrote:
> > > >
> > > > > Thanks Manikumar!
> > > > >
> > > > > +1
> > > > >
> > > > > Best,
> > > > > Bruno
> > > > >
> > > > > On 3/13/24 5:56 PM, Josep Prat wrote:
> > > > > > +1 thanks for volunteering!
> > > > > >
> > > > > > Best
> > > > > > ---
> > > > > >
> > > > > > Josep Prat
> > > > > > Open Source Engineering Director, aivenjosep.p...@aiven.io   |
> > > > > > +491715557497 | aiven.io
> > > > > > Aiven Deutschland GmbH
> > > > > > Alexanderufer 3-7, 10117 Berlin
> > > > > > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> > > > > > Amtsgericht Charlottenburg, HRB 209739 B
> > > > > >
> > > > > > On Wed, Mar 13, 2024, 17:17 Divij Vaidya <
> divijvaidy...@gmail.com>
> > > > > wrote:
> > > > > >
> > > > > >> +1
> > > > > >>
> > > > > >> Thank you for volunteering.
> > > > > >>
> > > > > >> --
> > > > > >> Divij Vaidya
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >> On Wed, Mar 13, 2024 at 4:58 PM Justine Olshan
> > > > > >> <jols...@confluent.io.invalid>
> > > > > >> wrote:
> > > > > >>
> > > > > >>> Thanks Manikumar!
> > > > > >>> +1 from me
> > > > > >>>
> > > > > >>> Justine
> > > > > >>>
> > > > > >>> On Wed, Mar 13, 2024 at 8:52 AM Manikumar <
> > > manikumar.re...@gmail.com>
> > > > > >>> wrote:
> > > > > >>>
> > > > > >>>> Hi,
> > > > > >>>>
> > > > > >>>> I'd like to volunteer to be the release manager for a bug fix
> > > release
> > > > > >> of
> > > > > >>>> the 3.6 line.
> > > > > >>>> If there are no objections, I'll send out the release plan
> soon.
> > > > > >>>>
> > > > > >>>> Thanks,
> > > > > >>>> Manikumar
> > > > > >>>>
> > > > > >>>
> > > > > >>
> > > > > >
> > > > >
> > >
> >
>

Reply via email to