Confused now -

I was praying that https://issues.apache.org/jira/browse/KAFKA-17078 would
be in this release! This is about SecurityManager.

If not in this 3.9.1 release, will there be another 3.9.x release soon?

Maybe I read this wrong, but it looked like the backport was trivial. We
are using Kafka as 3rd and 4th party dependency and the SecurityManager
piece is blocking us moving us to Java 24.

Hope it is not too late to still get it in.

- Jan.



On 2025/04/10 09:17:32 Anton Agestam wrote:
> Hi Luke,
>
> Thanks for the work on this release. I would have liked to see this PR
> included, but I guess the train was missed for this one. Is it possible to
> get some attention to this for the next release?
>
> https://github.com/apache/kafka/pull/17930
>
> Thanks,
>
> Den ons 9 apr. 2025 kl 14:17 skrev Luke Chen <sh...@gmail.com>:
>
> > Hi all,
> >
> > As discussed, today is the code freeze date for v3.9.1.
> > I should start to prepare for the RC build this Friday.
> >
> > Please let me know if you have any concerns.
> >
> > Thanks.
> > Luke
> >
> > On Tue, Apr 1, 2025 at 5:43 PM Edoardo Comar <ed...@gmail.com>
> > wrote:
> >
> > > Hi I'd like this fix to make it in 3.9.1
> > > https://github.com/apache/kafka/pull/19263
> > > any review to push it through  would be welcome - thanks
> > >
> > >
> > > On Fri, 28 Mar 2025 at 02:45, Luke Chen <sh...@gmail.com> wrote:
> > > >
> > > > Hi Stig,
> > > >
> > > > Let's make sure we have consensus from the community for this
> > backporting
> > > > first.
> > > > I've just replied in this thread:
> > > > https://lists.apache.org/thread/6k942pphowd28dh9gn6xbnngk6nxs3n0
> > > >
> > > > Thanks.
> > > > Luke
> > > >
> > > > On Fri, Mar 28, 2025 at 8:08 AM Matthias J. Sax <mj...@apache.org>
> > > wrote:
> > > >
> > > > > We don't need a new ticket. We can just add `3.9.1` as fixed
version
> > > > > after the PR is merged.
> > > > >
> > > > >
> > > > > -Matthias
> > > > >
> > > > >
> > > > > On 3/27/25 8:29 PM, Stig Rohde Døssing wrote:
> > > > > > I'd like to have https://github.com/apache/kafka/pull/19221
> > > included if
> > > > > > possible. Do you need me to open a new ticket for the backport,
> > > separate
> > > > > > from the original for 4.0.0 at
> > > > > > https://issues.apache.org/jira/browse/KAFKA-17078?
> > > > > >
> > > > > > Den tors. 27. mar. 2025 kl. 03.03 skrev Luke Chen <
> > show...@gmail.com
> > > >:
> > > > > >
> > > > > >> Hi Matthias,
> > > > > >>
> > > > > >> Thanks for your suggestion.
> > > > > >> The code freeze date will be *9 April 2025 *(Wednesday).
> > > > > >> I've also updated the release plan page.
> > > > > >>
> > > > > >> Thanks.
> > > > > >> Luke
> > > > > >>
> > > > > >> On Thu, Mar 27, 2025 at 2:15 AM Matthias J. Sax <
mj...@apache.org
> > >
> > > > > wrote:
> > > > > >>
> > > > > >>> Thanks Luke,
> > > > > >>>
> > > > > >>> Sounds like a good plan. I just added three more tickets that
I
> > > would
> > > > > >>> like to include in the release.
> > > > > >>>
> > > > > >>> Can you give a more concrete date when you want to create the
> > > first RC?
> > > > > >>> Having a concrete date (even if if might shift a little bit),
is
> > > > > usually
> > > > > >>> more helpful for people to plan getting bug fixes merged on
time;
> > > "by
> > > > > >>> mid of April" might be a little bit too fuzzy.
> > > > > >>>
> > > > > >>>
> > > > > >>> -Matthias
> > > > > >>>
> > > > > >>> On 3/24/25 3:50 PM, Luke Chen wrote:
> > > > > >>>> Hi all,
> > > > > >>>>
> > > > > >>>> I'll be the release manager for a bug fix release of the
3.9.1
> > > > > release.
> > > > > >>>>
> > > > > >>>> Here you have the release plan for 3.9.1:
> > > > > >>>>
> > > https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+3.9.1
> > > > > >>>>
> > > > > >>>> I'm aiming to have the first release candidate *by the mid of
> > > April*
> > > > > >>> since
> > > > > >>>> there are still some opening issues in v3.9.1. Let me know if
> > you
> > > have
> > > > > >>> any
> > > > > >>>> questions/concerns about the schedule.
> > > > > >>>>
> > > > > >>>> Thanks.
> > > > > >>>> Luke
> > > > > >>>>
> > > > > >>>
> > > > > >>>
> > > > > >>
> > > > > >
> > > > >
> > > > >
> > >
> >
>

Reply via email to