Hi,

Ok, I've put together a release plan:
https://cwiki.apache.org/confluence/display/KAFKA/Release+plan+3.6.1

I'll start chasing the owners of the few open issues. If there's any
other issues you'd like to have in 3.6.1, please let me know.

Thanks,
Mickael

On Mon, Nov 13, 2023 at 4:26 PM Divij Vaidya <[email protected]> wrote:
>
> Thanks for volunteering Mickael. Please feel free to take over this thread.
>
> From a Tiered Storage perspective, there is a long list of known bugs in
> 3.6.0 [1] but we shouldn't wait on fixing them all for 3.6.1. This should
> be ok since this feature is in early access. We will do a best-effort to
> merge some of the critical ones by next week. I will nudge the contributors
> where things are pending for a while.
>
> [1] https://issues.apache.org/jira/browse/KAFKA-15420
>
> --
> Divij Vaidya
>
>
>
> On Mon, Nov 13, 2023 at 4:10 PM Mickael Maison <[email protected]>
> wrote:
>
> > Hi Divij,
> >
> > You beat me to it, I was about to propose doing a 3.6.1 release later this
> > week.
> > While there's only a dozen or so issues fixed since 3.6.0, as
> > mentioned there's a few important dependency upgrades that would be
> > good to release.
> >
> > I'm happy to volunteer to run the release if we agree to releasing
> > sooner than initially proposed.
> > There seems to only be a few unresolved Jiras targeting 3.6.1 [0] (all
> > have PRs with some of them even already merged!).
> >
> > 0:
> > https://issues.apache.org/jira/browse/KAFKA-15552?jql=project%20%3D%20KAFKA%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%203.6.1%20ORDER%20BY%20priority%20DESC%2C%20status%20DESC%2C%20updated%20DESC
> >
> > Thanks,
> > Mickael
> >
> > On Mon, Nov 13, 2023 at 3:57 PM Divij Vaidya <[email protected]>
> > wrote:
> > >
> > > Hi Ismael, I am all-in favour for frequent releases. Sooner is always
> > > better. Unfortunately, I won't have bandwidth to volunteer for a release
> > in
> > > December. If someone else volunteers to be RM prior to this timeline, I
> > > would be happy to ceed the RM role to them but in the worst case
> > scenario,
> > > my offer to volunteer for Jan release could be considered as a backup.
> > >
> > > --
> > > Divij Vaidya
> > >
> > >
> > >
> > > On Mon, Nov 13, 2023 at 3:40 PM Ismael Juma <[email protected]> wrote:
> > >
> > > > Hi Divij,
> > > >
> > > > I think we should be releasing 3.6.1 this year rather than next. There
> > are
> > > > some critical bugs in 3.6.0 and I don't think we should be waiting that
> > > > long to fix them. What do you think?
> > > >
> > > > Ismael
> > > >
> > > > On Mon, Nov 13, 2023 at 6:32 AM Divij Vaidya <[email protected]>
> > > > wrote:
> > > >
> > > > > Hey folks,
> > > > >
> > > > >
> > > > > I'd like to volunteer to be the release manager for a bug fix
> > release of
> > > > > the 3.6 line. This will be the first bug fix release of this line and
> > > > will
> > > > > be version 3.6.1. It would contain critical bug fixes for  features
> > such
> > > > as
> > > > > Transaction verification [1], will stabilize Tiered Storage early
> > access
> > > > > release [2] [3] and upgrade dependencies to fix CVEs such as Netty
> > [4]
> > > > and
> > > > > Zookeeper [5].
> > > > >
> > > > > If no one has any objections, I will send out a release plan latest
> > by
> > > > 23rd
> > > > > Dec 2023 with a tentative release in mid-Jan 2024. The release plan
> > will
> > > > > include a list of all of the fixes we are targeting for 3.6.1 along
> > with
> > > > > the detailed timeline.
> > > > >
> > > > > If anyone is interested in releasing this sooner, please feel free to
> > > > take
> > > > > over from me.
> > > > >
> > > > > Thanks!
> > > > >
> > > > > Regards,
> > > > > Divij Vaidya
> > > > > Apache Kafka Committer
> > > > >
> > > > > [1] https://issues.apache.org/jira/browse/KAFKA-15653
> > > > > [2] https://issues.apache.org/jira/browse/KAFKA-15481
> > > > > [3] https://issues.apache.org/jira/browse/KAFKA-15695
> > > > > [4] https://issues.apache.org/jira/browse/KAFKA-15644
> > > > > [5] https://issues.apache.org/jira/browse/KAFKA-15596
> > > > >
> > > >
> >

Reply via email to