Hi Mickael,

KIP-891 [1] is/was merged and feature complete before the 4.1 branch was
cut.
And the JIRA was resolved [2] but wasn't given a fix version (oops) so it's
not currently in the Release Plan.

Can I add KIP-891 to the Release Plan?

Thanks,
Greg

[1]
https://cwiki.apache.org/confluence/display/KAFKA/KIP-891%3A+Running+multiple+versions+of+Connector+plugins
[2] https://issues.apache.org/jira/browse/KAFKA-14410


On Thu, Jun 12, 2025 at 11:17 AM Mickael Maison <mickael.mai...@gmail.com>
wrote:

> Hi Justine,
>
> Ack, thanks for the update.
>
> Thanks,
> Mickael
>
> On Thu, Jun 12, 2025 at 6:44 PM Justine Olshan
> <jols...@confluent.io.invalid> wrote:
> >
> > Hey Mickael,
> >
> > Just a head's up, I'll be picking `KAFKA-19367: Fix InitProducerId with
> TV2
> > double-increments epoch if ongoing transaction is aborted` into 4.1.
> It's a
> > relatively small bug fix, and as reviewer, I'm pretty confident in the
> > testing behind it.
> >
> > Thanks
> > Justine
> >
> > On Thu, Jun 12, 2025 at 3:21 AM Mickael Maison <mickael.mai...@gmail.com
> >
> > wrote:
> >
> > > Hi José,
> > >
> > > Thanks for the update.
> > > I'm not really familiar with this KIP. If you can get it reviewed and
> > > merged this week and think it's not too risky to merge this now, go
> > > ahead and cherry-pick it to 4.1.
> > >
> > > Thanks,
> > > Mickael
> > >
> > > On Wed, Jun 11, 2025 at 10:02 PM José Armando García Sancio
> > > <jsan...@confluent.io.invalid> wrote:
> > > >
> > > > Hi Mickael,
> > > >
> > > > Thanks for working on the release. I have a PR for faster HWM
> > > > propagation for the kraft cluster metadata partition. I expect the PR
> > > > to get merged this week. Can I cherry pick it to the 4.1 branch when
> > > > it is merged?
> > > >
> > > > PR: https://github.com/apache/kafka/pull/19800
> > > >
> > > > Thanks,
> > > >
> > > > On Tue, Jun 10, 2025 at 2:03 PM Mickael Maison <
> mickael.mai...@gmail.com>
> > > wrote:
> > > > >
> > > > > Hi Chia-Ping,
> > > > >
> > > > > There isn't anything specific to 4.1.0, same rules as usual apply.
> > > > >
> > > > > After feature freeze, we shouldn't merge new major features into
> 4.1.
> > > > > Stabilization fixes are fine.
> > > > > There is some flexibility with minor features but always
> communicate
> > > > > and ask in the release thread (here).
> > > > > Bug fixes can be backported especially blockers, regressions and
> > > > > dependency updates to mitigate CVEs.
> > > > >
> > > > > Again if you're unsure, feel free to tag me in PRs or ask here.
> > > > >
> > > > > The next milestone is code freeze on May 25.
> > > > >
> > > > > Thanks,
> > > > > Mickael
> > > > >
> > > > >
> > > > > On Tue, Jun 10, 2025 at 6:35 PM Chia-Ping Tsai <chia7...@gmail.com
> >
> > > wrote:
> > > > > >
> > > > > > hi Mickael
> > > > > >
> > > > > > Thanks for managing the 4.1 branch.
> > > > > > Are there any rules of backporting to 4.1 that we need to know?
> > > > > >
> > > > > > Best,
> > > > > > Chia-Ping
> > > > > >
> > > > > >
> > > > > > Mickael Maison <mickael.mai...@gmail.com> 於 2025年6月10日 週二
> 下午11:47寫道:
> > > > > >
> > > > > > > Hi,
> > > > > > >
> > > > > > > With the help of Infra I was able to create the new 4.1 branch:
> > > > > > > https://github.com/apache/kafka/tree/4.1
> > > > > > > I'll explain the issue I found in another thread.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Mickael
> > > > > > >
> > > > > > > On Tue, Jun 10, 2025 at 2:53 PM Mickael Maison <
> > > mickael.mai...@gmail.com>
> > > > > > > wrote:
> > > > > > > >
> > > > > > > > Hi,
> > > > > > > >
> > > > > > > > We are now past feature freeze.
> > > > > > > > My plan was to cut the 4.1 branch today, but with the new
> branch
> > > > > > > > protection rules we set [0] I'm not able to do so at the
> moment.
> > > I
> > > > > > > > opened a Jira against Infra [1] and hopefully that will be
> sorted
> > > > > > > > soon.
> > > > > > > >
> > > > > > > > I'll post another update once the branch is cut.
> > > > > > > >
> > > > > > > > Thanks,
> > > > > > > > Mickael
> > > > > > > >
> > > > > > > > 0: https://issues.apache.org/jira/browse/INFRA-26603
> > > > > > > > 1: https://issues.apache.org/jira/browse/INFRA-26900
> > > > > > > >
> > > > > > > > On Mon, Jun 2, 2025 at 10:46 AM Mickael Maison <
> > > mickael.mai...@gmail.com>
> > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > Hi PoAn,
> > > > > > > > >
> > > > > > > > > Since both KIPs were accepted before the deadline I've
> added
> > > them to
> > > > > > > > > the release plan. In the future feel free to edit the
> release
> > > plan
> > > > > > > > > yourself.
> > > > > > > > >
> > > > > > > > > Note that feature freeze is this week, so the goal is to
> merge
> > > all
> > > > > > > > > KIP-related code by the end of the week. If that's not
> > > possible let me
> > > > > > > > > know.
> > > > > > > > >
> > > > > > > > > Thanks,
> > > > > > > > > Mickael
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On Mon, Jun 2, 2025 at 9:14 AM PoAn Yang <
> yangp...@gmail.com>
> > > wrote:
> > > > > > > > > >
> > > > > > > > > > Hi Mickael,
> > > > > > > > > >
> > > > > > > > > > May I add KIP-1101 (
> > > https://cwiki.apache.org/confluence/x/FouMEw)
> > > > > > > and
> > > > > > > > > > KIP-1142 (https://cwiki.apache.org/confluence/x/AAqWF)
> to
> > > release
> > > > > > > plan?
> > > > > > > > > > These KIPs were accepted on April 17th and April 29th.
> I’m
> > > sorry for
> > > > > > > not
> > > > > > > > > > adding them to the release plan when they were accepted.
> > > > > > > > > >
> > > > > > > > > > For KIP-1101, we already merged consumer group PRs.
> > > Remaining PRs
> > > > > > > > > > are for share / stream groups and one for integration
> test.
> > > They’re
> > > > > > > all ready
> > > > > > > > > > for reviewing:
> > > > > > > > > > * https://github.com/apache/kafka/pull/19802
> > > > > > > > > > * https://github.com/apache/kafka/pull/19796
> > > > > > > > > > * https://github.com/apache/kafka/pull/19856
> > > > > > > > > >
> > > > > > > > > > For KIP-1142, it's almost finished. One remaining PR is
> about
> > > > > > > compatibility
> > > > > > > > > > of missing metric.
> > > > > > > > > > * https://github.com/apache/kafka/pull/19877
> > > > > > > > > >
> > > > > > > > > > Thanks,
> > > > > > > > > > PoAn
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > > On May 14, 2025, at 6:20 PM, Mickael Maison <
> > > > > > > mickael.mai...@gmail.com> wrote:
> > > > > > > > > > >
> > > > > > > > > > > Hi,
> > > > > > > > > > >
> > > > > > > > > > > Reminder that today is KIP freeze.
> > > > > > > > > > > If you have a KIP that has been approved before the
> end of
> > > the day,
> > > > > > > > > > > you can add it to the 4.1.0 release plan.
> > > > > > > > > > >
> > > > > > > > > > > The next milestone is feature freeze on June 4.
> > > > > > > > > > >
> > > > > > > > > > > Thanks,
> > > > > > > > > > > Mickael
> > > > > > > > > > >
> > > > > > > > > > > On Tue, May 13, 2025 at 6:48 PM Mickael Maison <
> > > > > > > mickael.mai...@gmail.com> wrote:
> > > > > > > > > > >>
> > > > > > > > > > >> Hi Kirk,
> > > > > > > > > > >> Yes it was approved before KIP freeze, so feel free to
> > > add it to
> > > > > > > the
> > > > > > > > > > >> release plan. (I would have done it now but the wiki
> > > seems to be
> > > > > > > down
> > > > > > > > > > >> at the moment)
> > > > > > > > > > >>
> > > > > > > > > > >> Hi Jose,
> > > > > > > > > > >> Ack
> > > > > > > > > > >>
> > > > > > > > > > >> Thanks,
> > > > > > > > > > >> Mickael
> > > > > > > > > > >>
> > > > > > > > > > >> On Tue, May 13, 2025 at 6:17 PM José Armando García
> Sancio
> > > > > > > > > > >> <jsan...@confluent.io.invalid> wrote:
> > > > > > > > > > >>>
> > > > > > > > > > >>> HI Mickael,
> > > > > > > > > > >>>
> > > > > > > > > > >>> I have added "KIP-1166: Improve high-watermark
> > > replication" to
> > > > > > > the
> > > > > > > > > > >>> 4.1.0 release wiki page.
> > > > > > > > > > >>>
> > > > > > > > > > >>> Thanks,
> > > > > > > > > > >>> --
> > > > > > > > > > >>> -José
> > > > > > > > > >
> > > > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > -José
> > >
>

Reply via email to