You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by Kirk True <ki...@kirktrue.pro> on 2025/05/07 22:31:57 UTC

Re: [DISCUSS] Apache Kafka 4.1.0 release

Hi Mickael,

Can we add KIP-1139 (https://cwiki.apache.org/confluence/x/uIxEF) to the 4.1.0 "Planned KIP Content" list? It was approved yesterday.

Thanks,
Kirk

On Wed, Mar 19, 2025, at 4:58 AM, Mickael Maison wrote:
> Hi,
> 
> I'd like to volunteer to be the release manager for the Apache Kafka
> 4.1.0 release.
> 
> If there are no objections, I'll start building the release plan in
> the next few days.
> 
> Thanks,
> Mickael
>

Re: [DISCUSS] Apache Kafka 4.1.0 release

Posted by Mickael Maison <mi...@gmail.com>.

Hi,

Update on the release process:
- Infra has removed the "require linear history" branch protection
rule from our repository, so I've been able to push the 4.1.0-rc0 tag
- The jvm docker image has finally appeared on DockerHub, it took
several hours after the GitHub action succeeded, but it's now there
and it works
- The Docker Build Test action for the native image is failing. See
the last run [0]. Tweaking a few things I managed to run the action
locally and it seemed to work, so I decided to still run the Build and
Push Release Candidate Docker Image action [1] on it. But when I
tested this image pushed to DockerHub [2] it did not work. I opened
https://issues.apache.org/jira/browse/KAFKA-19495 to track that issue,
this is probably why the Docker Build Test action is failing.

Help from someone familiar with the native image build would be really
appreciated. Especially if we need to update the native-image-configs
files, I'm afraid I don't have an environment that can be used to
generate them.

0: https://github.com/apache/kafka/actions/runs/16190660272
1: https://github.com/apache/kafka/actions/runs/16196532977/job/45724349624
2: https://hub.docker.com/layers/apache/kafka-native/4.1.0-rc0/images/sha256-dd69cac8a2aa1282e42b25f92d2a66f29c6a6bf375bc8759b9728b2d2c0561c7

Thanks,
Mickael


On Wed, Jul 9, 2025 at 6:25 PM Mickael Maison <mi...@gmail.com> wrote:
>
> Hi,
>
> Another issue.
> In order to fix https://issues.apache.org/jira/browse/KAFKA-19166 we
> now do a git merge with the tag in the release script.
> However our repository is configured to require linear history and
> thus rejects any merge commits. This is the same issue I hit last
> month when creating the 4.1 branch
> https://issues.apache.org/jira/browse/INFRA-26900
>
> I asked the Infra team to disable that branch protection rule.
>
> Thanks,
> Mickael
>
>
> On Wed, Jul 9, 2025 at 5:20 PM Mickael Maison <mi...@gmail.com> wrote:
> >
> > Hi,
> >
> > Quick update on the release. I started the release process for the
> > first RC today.
> >
> > I ran the release script, generated the release artifacts and pushed
> > them to dist and nexus:
> > - https://dist.apache.org/repos/dist/dev/kafka/4.1.0-rc0/
> > - https://repository.apache.org/content/groups/staging/org/apache/kafka/kafka_2.13/4.1.0/
> >
> > However I'm having trouble with the Docker images.
> > The jvm image is building fine, passed the tests and the Build and
> > Push Release Candidate Docker Image [0] action succeeded in GitHub but
> > I don't see the image on DockerHub [1]
> > The native image is building but fails to pass the tests [2]
> >
> > I'm currently investigating these issues. If you have any insights, let me know!
> >
> > 0: https://github.com/apache/kafka/actions/runs/16172935878/job/45650895003
> > 1: https://hub.docker.com/r/apache/kafka/tags
> > 2: https://github.com/apache/kafka/actions/runs/16172695273/job/45650048500
> >
> > Thanks,
> > Mickael
> >
> > On Mon, Jul 7, 2025 at 10:34 AM Chia-Ping Tsai <ch...@apache.org> wrote:
> > >
> > > for another, I backported https://github.com/apache/kafka/commit/f14e60fc8fa9bbffcd1b46b899a0cbb17f24745d, which is just a test migration, to reduce the conflicts when backporting KAFKA-19397
> > >
> > > On 2025/07/07 08:22:54 Chia-Ping Tsai wrote:
> > > > hi Mickael
> > > >
> > > > I have merged https://github.com/apache/kafka/pull/20112 to enable CI to run for branch 4.1
> > > >
> > > > Also, I will backport KAFKA-19397 (https://github.com/apache/kafka/pull/20109) to branch 4.1 if CI looks good.
> > > >
> > > > Best,
> > > > Chia-Ping
> > > >
> > > > On 2025/06/10 12:53:16 Mickael Maison 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 <mi...@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 <ya...@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 <mi...@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 <mi...@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
> > > > > > > >> <js...@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é
> > > > > > >
> > > > >
> > > >

Re: [DISCUSS] Apache Kafka 4.1.0 release

Posted by Mickael Maison <mi...@gmail.com>.

Hi,

Another issue.
In order to fix https://issues.apache.org/jira/browse/KAFKA-19166 we
now do a git merge with the tag in the release script.
However our repository is configured to require linear history and
thus rejects any merge commits. This is the same issue I hit last
month when creating the 4.1 branch
https://issues.apache.org/jira/browse/INFRA-26900

I asked the Infra team to disable that branch protection rule.

Thanks,
Mickael


On Wed, Jul 9, 2025 at 5:20 PM Mickael Maison <mi...@gmail.com> wrote:
>
> Hi,
>
> Quick update on the release. I started the release process for the
> first RC today.
>
> I ran the release script, generated the release artifacts and pushed
> them to dist and nexus:
> - https://dist.apache.org/repos/dist/dev/kafka/4.1.0-rc0/
> - https://repository.apache.org/content/groups/staging/org/apache/kafka/kafka_2.13/4.1.0/
>
> However I'm having trouble with the Docker images.
> The jvm image is building fine, passed the tests and the Build and
> Push Release Candidate Docker Image [0] action succeeded in GitHub but
> I don't see the image on DockerHub [1]
> The native image is building but fails to pass the tests [2]
>
> I'm currently investigating these issues. If you have any insights, let me know!
>
> 0: https://github.com/apache/kafka/actions/runs/16172935878/job/45650895003
> 1: https://hub.docker.com/r/apache/kafka/tags
> 2: https://github.com/apache/kafka/actions/runs/16172695273/job/45650048500
>
> Thanks,
> Mickael
>
> On Mon, Jul 7, 2025 at 10:34 AM Chia-Ping Tsai <ch...@apache.org> wrote:
> >
> > for another, I backported https://github.com/apache/kafka/commit/f14e60fc8fa9bbffcd1b46b899a0cbb17f24745d, which is just a test migration, to reduce the conflicts when backporting KAFKA-19397
> >
> > On 2025/07/07 08:22:54 Chia-Ping Tsai wrote:
> > > hi Mickael
> > >
> > > I have merged https://github.com/apache/kafka/pull/20112 to enable CI to run for branch 4.1
> > >
> > > Also, I will backport KAFKA-19397 (https://github.com/apache/kafka/pull/20109) to branch 4.1 if CI looks good.
> > >
> > > Best,
> > > Chia-Ping
> > >
> > > On 2025/06/10 12:53:16 Mickael Maison 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 <mi...@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 <ya...@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 <mi...@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 <mi...@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
> > > > > > >> <js...@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é
> > > > > >
> > > >
> > >

Re: [DISCUSS] Apache Kafka 4.1.0 release

Posted by Mickael Maison <mi...@gmail.com>.

Hi,

Quick update on the release. I started the release process for the
first RC today.

I ran the release script, generated the release artifacts and pushed
them to dist and nexus:
- https://dist.apache.org/repos/dist/dev/kafka/4.1.0-rc0/
- https://repository.apache.org/content/groups/staging/org/apache/kafka/kafka_2.13/4.1.0/

However I'm having trouble with the Docker images.
The jvm image is building fine, passed the tests and the Build and
Push Release Candidate Docker Image [0] action succeeded in GitHub but
I don't see the image on DockerHub [1]
The native image is building but fails to pass the tests [2]

I'm currently investigating these issues. If you have any insights, let me know!

0: https://github.com/apache/kafka/actions/runs/16172935878/job/45650895003
1: https://hub.docker.com/r/apache/kafka/tags
2: https://github.com/apache/kafka/actions/runs/16172695273/job/45650048500

Thanks,
Mickael

On Mon, Jul 7, 2025 at 10:34 AM Chia-Ping Tsai <ch...@apache.org> wrote:
>
> for another, I backported https://github.com/apache/kafka/commit/f14e60fc8fa9bbffcd1b46b899a0cbb17f24745d, which is just a test migration, to reduce the conflicts when backporting KAFKA-19397
>
> On 2025/07/07 08:22:54 Chia-Ping Tsai wrote:
> > hi Mickael
> >
> > I have merged https://github.com/apache/kafka/pull/20112 to enable CI to run for branch 4.1
> >
> > Also, I will backport KAFKA-19397 (https://github.com/apache/kafka/pull/20109) to branch 4.1 if CI looks good.
> >
> > Best,
> > Chia-Ping
> >
> > On 2025/06/10 12:53:16 Mickael Maison 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 <mi...@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 <ya...@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 <mi...@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 <mi...@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
> > > > > >> <js...@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é
> > > > >
> > >
> >

Re: [DISCUSS] Apache Kafka 4.1.0 release

Posted by Chia-Ping Tsai <ch...@apache.org>.

for another, I backported https://github.com/apache/kafka/commit/f14e60fc8fa9bbffcd1b46b899a0cbb17f24745d, which is just a test migration, to reduce the conflicts when backporting KAFKA-19397

On 2025/07/07 08:22:54 Chia-Ping Tsai wrote:
> hi Mickael
> 
> I have merged https://github.com/apache/kafka/pull/20112 to enable CI to run for branch 4.1
> 
> Also, I will backport KAFKA-19397 (https://github.com/apache/kafka/pull/20109) to branch 4.1 if CI looks good.
> 
> Best,
> Chia-Ping
> 
> On 2025/06/10 12:53:16 Mickael Maison 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 <mi...@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 <ya...@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 <mi...@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 <mi...@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
> > > > >> <js...@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é
> > > >
> > 
>

Re: [DISCUSS] Apache Kafka 4.1.0 release

Posted by Chia-Ping Tsai <ch...@apache.org>.

hi Mickael

I have merged https://github.com/apache/kafka/pull/20112 to enable CI to run for branch 4.1

Also, I will backport KAFKA-19397 (https://github.com/apache/kafka/pull/20109) to branch 4.1 if CI looks good.

Best,
Chia-Ping

On 2025/06/10 12:53:16 Mickael Maison 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 <mi...@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 <ya...@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 <mi...@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 <mi...@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
> > > >> <js...@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é
> > >
>

Re: [DISCUSS] Apache Kafka 4.1.0 release

Posted by Apoorv Mittal <ap...@gmail.com>.

Thanks, the PR is merged.

Regards,
Apoorv Mittal


On Thu, Jul 3, 2025 at 7:11 PM Mickael Maison <mi...@gmail.com>
wrote:

> Hi Apoorv,
>
> Yes you can go ahead and merge it in 4.1.
>
> Thanks,
> Mickael
>
> On Thu, Jul 3, 2025 at 6:48 PM Apoorv Mittal <ap...@gmail.com>
> wrote:
> >
> > Hi Mickael,
> > We've found an issue within share groups where the failure to replay
> > certain records can impact the replay of records for other groups in the
> > same group coordinator shard, potentially disrupting other groups as
> well:
> > https://issues.apache.org/jira/browse/KAFKA-19453. The code is merged in
> > trunk and patch for 4.1 is available:
> > https://github.com/apache/kafka/pull/20100.
> >
> > Please let me know if I can merge it to the 4.1 branch.
> >
> > Regards,
> > Apoorv Mittal
> >
> >
> > On Wed, Jul 2, 2025 at 5:19 PM Andrew Schofield <
> > andrew_schofield_jira@outlook.com> wrote:
> >
> > > Thanks. PR merged into 4.1.
> > >
> > > Andrew
> > >
> > > ________________________________________
> > > From: Mickael Maison <mi...@gmail.com>
> > > Sent: 02 July 2025 16:29
> > > To: dev@kafka.apache.org <de...@kafka.apache.org>
> > > Subject: Re: [DISCUSS] Apache Kafka 4.1.0 release
> > >
> > > Hi Andrew,
> > >
> > > Feel free to backport to 4.1.
> > >
> > > Thanks,
> > > Mickael
> > >
> > > On Wed, Jul 2, 2025 at 4:55 PM Andrew Schofield
> > > <an...@outlook.com> wrote:
> > > >
> > > > Hi Mickael,
> > > > We have found an NPE in the group coordinator while stress testing
> which
> > > should probably be fixed.
> > > > There is a chance that a topic being looked up is not present in the
> > > metadata image
> > > > in GroupCoordinatorService.onPartitionsDeleted. This is KAFKA-19454.
> > > >
> > > > Here's the trunk PR https://github.com/apache/kafka/pull/20090.
> > > >
> > > > Let me know what you think. We can have a more targeted 4.1 PR ready
> in
> > > moments.
> > > >
> > > > Thanks,
> > > > Andrew
> > > > ________________________________________
> > > > From: Mickael Maison <mi...@gmail.com>
> > > > Sent: 01 July 2025 14:58
> > > > To: dev@kafka.apache.org <de...@kafka.apache.org>
> > > > Subject: Re: [DISCUSS] Apache Kafka 4.1.0 release
> > > >
> > > > Hi,
> > > >
> > > > Quick update on the status of 4.1.0.
> > > >
> > > > We are down to 3 open Jiras:
> > > > - KAFKA-19221: This is fixed in trunk and 4.1. The Jira is just
> opened
> > > > while the backport to 4.0 is happening.
> > > > - KAFKA-19184: This is a doc update for migrating static to dynamic
> > > > quorums. The PR is under review.
> > > > - KAFKA-19397: We don't have a fix at the moment but people are
> > > > actively working on it.
> > > >
> > > > Thanks,
> > > > Mickael
> > > >
> > > > On Wed, Jun 25, 2025 at 3:41 PM Mickael Maison <
> mickael.maison@gmail.com>
> > > wrote:
> > > > >
> > > > > Hi,
> > > > >
> > > > > Today is code freeze. I've started moving unresolved tickets
> targeting
> > > > > 4.1.0 to 4.2.0.
> > > > > The only exceptions are for blockers, fixing flaky tests or adding
> > > > > docs for a new feature. For anything else, please ask me before
> > > > > applying it to the 4.1 branch.
> > > > >
> > > > > Thanks,
> > > > > Mickael
> > > > >
> > > > >
> > > > > On Wed, Jun 18, 2025 at 12:14 PM Mickael Maison
> > > > > <mi...@gmail.com> wrote:
> > > > > >
> > > > > > Hi Greg,
> > > > > >
> > > > > > The release plan must match what we ship!
> > > > > > So if KIP-891 has already been merged and is in 4.1, yes it
> should be
> > > > > > part of the release plan.
> > > > > >
> > > > > > I've added it to the release plan.
> > > > > >
> > > > > > Thanks,
> > > > > > Mickael
> > > > > >
> > > > > > On Tue, Jun 17, 2025 at 6:06 PM Greg Harris
> > > > > > <gr...@aiven.io.invalid> wrote:
> > > > > > >
> > > > > > > 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.maison@gmail.com>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Hi Justine,
> > > > > > > >
> > > > > > > > Ack, thanks for the update.
> > > > > > > >
> > > > > > > > Thanks,
> > > > > > > > Mickael
> > > > > > > >
> > > > > > > > On Thu, Jun 12, 2025 at 6:44 PM Justine Olshan
> > > > > > > > <jo...@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.maison@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
> > > > > > > > > > <js...@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.maison@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 <
> > > chia7712@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 <mi...@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.maison@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.maison@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 <
> > > > > > > > yangpoan@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.maison@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.maison@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
> > > > > > > > > > > > > > > > > >> <js...@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é
> > > > > > > > > >
> > > > > > > >
> > >
>

Re: [DISCUSS] Apache Kafka 4.1.0 release

Posted by Mickael Maison <mi...@gmail.com>.

Hi Apoorv,

Yes you can go ahead and merge it in 4.1.

Thanks,
Mickael

On Thu, Jul 3, 2025 at 6:48 PM Apoorv Mittal <ap...@gmail.com> wrote:
>
> Hi Mickael,
> We've found an issue within share groups where the failure to replay
> certain records can impact the replay of records for other groups in the
> same group coordinator shard, potentially disrupting other groups as well:
> https://issues.apache.org/jira/browse/KAFKA-19453. The code is merged in
> trunk and patch for 4.1 is available:
> https://github.com/apache/kafka/pull/20100.
>
> Please let me know if I can merge it to the 4.1 branch.
>
> Regards,
> Apoorv Mittal
>
>
> On Wed, Jul 2, 2025 at 5:19 PM Andrew Schofield <
> andrew_schofield_jira@outlook.com> wrote:
>
> > Thanks. PR merged into 4.1.
> >
> > Andrew
> >
> > ________________________________________
> > From: Mickael Maison <mi...@gmail.com>
> > Sent: 02 July 2025 16:29
> > To: dev@kafka.apache.org <de...@kafka.apache.org>
> > Subject: Re: [DISCUSS] Apache Kafka 4.1.0 release
> >
> > Hi Andrew,
> >
> > Feel free to backport to 4.1.
> >
> > Thanks,
> > Mickael
> >
> > On Wed, Jul 2, 2025 at 4:55 PM Andrew Schofield
> > <an...@outlook.com> wrote:
> > >
> > > Hi Mickael,
> > > We have found an NPE in the group coordinator while stress testing which
> > should probably be fixed.
> > > There is a chance that a topic being looked up is not present in the
> > metadata image
> > > in GroupCoordinatorService.onPartitionsDeleted. This is KAFKA-19454.
> > >
> > > Here's the trunk PR https://github.com/apache/kafka/pull/20090.
> > >
> > > Let me know what you think. We can have a more targeted 4.1 PR ready in
> > moments.
> > >
> > > Thanks,
> > > Andrew
> > > ________________________________________
> > > From: Mickael Maison <mi...@gmail.com>
> > > Sent: 01 July 2025 14:58
> > > To: dev@kafka.apache.org <de...@kafka.apache.org>
> > > Subject: Re: [DISCUSS] Apache Kafka 4.1.0 release
> > >
> > > Hi,
> > >
> > > Quick update on the status of 4.1.0.
> > >
> > > We are down to 3 open Jiras:
> > > - KAFKA-19221: This is fixed in trunk and 4.1. The Jira is just opened
> > > while the backport to 4.0 is happening.
> > > - KAFKA-19184: This is a doc update for migrating static to dynamic
> > > quorums. The PR is under review.
> > > - KAFKA-19397: We don't have a fix at the moment but people are
> > > actively working on it.
> > >
> > > Thanks,
> > > Mickael
> > >
> > > On Wed, Jun 25, 2025 at 3:41 PM Mickael Maison <mi...@gmail.com>
> > wrote:
> > > >
> > > > Hi,
> > > >
> > > > Today is code freeze. I've started moving unresolved tickets targeting
> > > > 4.1.0 to 4.2.0.
> > > > The only exceptions are for blockers, fixing flaky tests or adding
> > > > docs for a new feature. For anything else, please ask me before
> > > > applying it to the 4.1 branch.
> > > >
> > > > Thanks,
> > > > Mickael
> > > >
> > > >
> > > > On Wed, Jun 18, 2025 at 12:14 PM Mickael Maison
> > > > <mi...@gmail.com> wrote:
> > > > >
> > > > > Hi Greg,
> > > > >
> > > > > The release plan must match what we ship!
> > > > > So if KIP-891 has already been merged and is in 4.1, yes it should be
> > > > > part of the release plan.
> > > > >
> > > > > I've added it to the release plan.
> > > > >
> > > > > Thanks,
> > > > > Mickael
> > > > >
> > > > > On Tue, Jun 17, 2025 at 6:06 PM Greg Harris
> > > > > <gr...@aiven.io.invalid> wrote:
> > > > > >
> > > > > > 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.maison@gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > > > Hi Justine,
> > > > > > >
> > > > > > > Ack, thanks for the update.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Mickael
> > > > > > >
> > > > > > > On Thu, Jun 12, 2025 at 6:44 PM Justine Olshan
> > > > > > > <jo...@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.maison@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
> > > > > > > > > <js...@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.maison@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 <
> > chia7712@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 <mi...@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.maison@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.maison@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 <
> > > > > > > yangpoan@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.maison@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.maison@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
> > > > > > > > > > > > > > > > >> <js...@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é
> > > > > > > > >
> > > > > > >
> >

Re: [DISCUSS] Apache Kafka 4.1.0 release

Posted by Apoorv Mittal <ap...@gmail.com>.

Hi Mickael,
We've found an issue within share groups where the failure to replay
certain records can impact the replay of records for other groups in the
same group coordinator shard, potentially disrupting other groups as well:
https://issues.apache.org/jira/browse/KAFKA-19453. The code is merged in
trunk and patch for 4.1 is available:
https://github.com/apache/kafka/pull/20100.

Please let me know if I can merge it to the 4.1 branch.

Regards,
Apoorv Mittal


On Wed, Jul 2, 2025 at 5:19 PM Andrew Schofield <
andrew_schofield_jira@outlook.com> wrote:

> Thanks. PR merged into 4.1.
>
> Andrew
>
> ________________________________________
> From: Mickael Maison <mi...@gmail.com>
> Sent: 02 July 2025 16:29
> To: dev@kafka.apache.org <de...@kafka.apache.org>
> Subject: Re: [DISCUSS] Apache Kafka 4.1.0 release
>
> Hi Andrew,
>
> Feel free to backport to 4.1.
>
> Thanks,
> Mickael
>
> On Wed, Jul 2, 2025 at 4:55 PM Andrew Schofield
> <an...@outlook.com> wrote:
> >
> > Hi Mickael,
> > We have found an NPE in the group coordinator while stress testing which
> should probably be fixed.
> > There is a chance that a topic being looked up is not present in the
> metadata image
> > in GroupCoordinatorService.onPartitionsDeleted. This is KAFKA-19454.
> >
> > Here's the trunk PR https://github.com/apache/kafka/pull/20090.
> >
> > Let me know what you think. We can have a more targeted 4.1 PR ready in
> moments.
> >
> > Thanks,
> > Andrew
> > ________________________________________
> > From: Mickael Maison <mi...@gmail.com>
> > Sent: 01 July 2025 14:58
> > To: dev@kafka.apache.org <de...@kafka.apache.org>
> > Subject: Re: [DISCUSS] Apache Kafka 4.1.0 release
> >
> > Hi,
> >
> > Quick update on the status of 4.1.0.
> >
> > We are down to 3 open Jiras:
> > - KAFKA-19221: This is fixed in trunk and 4.1. The Jira is just opened
> > while the backport to 4.0 is happening.
> > - KAFKA-19184: This is a doc update for migrating static to dynamic
> > quorums. The PR is under review.
> > - KAFKA-19397: We don't have a fix at the moment but people are
> > actively working on it.
> >
> > Thanks,
> > Mickael
> >
> > On Wed, Jun 25, 2025 at 3:41 PM Mickael Maison <mi...@gmail.com>
> wrote:
> > >
> > > Hi,
> > >
> > > Today is code freeze. I've started moving unresolved tickets targeting
> > > 4.1.0 to 4.2.0.
> > > The only exceptions are for blockers, fixing flaky tests or adding
> > > docs for a new feature. For anything else, please ask me before
> > > applying it to the 4.1 branch.
> > >
> > > Thanks,
> > > Mickael
> > >
> > >
> > > On Wed, Jun 18, 2025 at 12:14 PM Mickael Maison
> > > <mi...@gmail.com> wrote:
> > > >
> > > > Hi Greg,
> > > >
> > > > The release plan must match what we ship!
> > > > So if KIP-891 has already been merged and is in 4.1, yes it should be
> > > > part of the release plan.
> > > >
> > > > I've added it to the release plan.
> > > >
> > > > Thanks,
> > > > Mickael
> > > >
> > > > On Tue, Jun 17, 2025 at 6:06 PM Greg Harris
> > > > <gr...@aiven.io.invalid> wrote:
> > > > >
> > > > > 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.maison@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > Hi Justine,
> > > > > >
> > > > > > Ack, thanks for the update.
> > > > > >
> > > > > > Thanks,
> > > > > > Mickael
> > > > > >
> > > > > > On Thu, Jun 12, 2025 at 6:44 PM Justine Olshan
> > > > > > <jo...@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.maison@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
> > > > > > > > <js...@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.maison@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 <
> chia7712@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 <mi...@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.maison@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.maison@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 <
> > > > > > yangpoan@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.maison@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.maison@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
> > > > > > > > > > > > > > > >> <js...@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é
> > > > > > > >
> > > > > >
>

Re: [DISCUSS] Apache Kafka 4.1.0 release

Posted by Andrew Schofield <an...@outlook.com>.

Thanks. PR merged into 4.1.

Andrew

________________________________________
From: Mickael Maison <mi...@gmail.com>
Sent: 02 July 2025 16:29
To: dev@kafka.apache.org <de...@kafka.apache.org>
Subject: Re: [DISCUSS] Apache Kafka 4.1.0 release

Hi Andrew,

Feel free to backport to 4.1.

Thanks,
Mickael

On Wed, Jul 2, 2025 at 4:55 PM Andrew Schofield
<an...@outlook.com> wrote:
>
> Hi Mickael,
> We have found an NPE in the group coordinator while stress testing which should probably be fixed.
> There is a chance that a topic being looked up is not present in the metadata image
> in GroupCoordinatorService.onPartitionsDeleted. This is KAFKA-19454.
>
> Here's the trunk PR https://github.com/apache/kafka/pull/20090.
>
> Let me know what you think. We can have a more targeted 4.1 PR ready in moments.
>
> Thanks,
> Andrew
> ________________________________________
> From: Mickael Maison <mi...@gmail.com>
> Sent: 01 July 2025 14:58
> To: dev@kafka.apache.org <de...@kafka.apache.org>
> Subject: Re: [DISCUSS] Apache Kafka 4.1.0 release
>
> Hi,
>
> Quick update on the status of 4.1.0.
>
> We are down to 3 open Jiras:
> - KAFKA-19221: This is fixed in trunk and 4.1. The Jira is just opened
> while the backport to 4.0 is happening.
> - KAFKA-19184: This is a doc update for migrating static to dynamic
> quorums. The PR is under review.
> - KAFKA-19397: We don't have a fix at the moment but people are
> actively working on it.
>
> Thanks,
> Mickael
>
> On Wed, Jun 25, 2025 at 3:41 PM Mickael Maison <mi...@gmail.com> wrote:
> >
> > Hi,
> >
> > Today is code freeze. I've started moving unresolved tickets targeting
> > 4.1.0 to 4.2.0.
> > The only exceptions are for blockers, fixing flaky tests or adding
> > docs for a new feature. For anything else, please ask me before
> > applying it to the 4.1 branch.
> >
> > Thanks,
> > Mickael
> >
> >
> > On Wed, Jun 18, 2025 at 12:14 PM Mickael Maison
> > <mi...@gmail.com> wrote:
> > >
> > > Hi Greg,
> > >
> > > The release plan must match what we ship!
> > > So if KIP-891 has already been merged and is in 4.1, yes it should be
> > > part of the release plan.
> > >
> > > I've added it to the release plan.
> > >
> > > Thanks,
> > > Mickael
> > >
> > > On Tue, Jun 17, 2025 at 6:06 PM Greg Harris
> > > <gr...@aiven.io.invalid> wrote:
> > > >
> > > > 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 <mi...@gmail.com>
> > > > wrote:
> > > >
> > > > > Hi Justine,
> > > > >
> > > > > Ack, thanks for the update.
> > > > >
> > > > > Thanks,
> > > > > Mickael
> > > > >
> > > > > On Thu, Jun 12, 2025 at 6:44 PM Justine Olshan
> > > > > <jo...@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.maison@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
> > > > > > > <js...@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.maison@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 <chia7712@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 <mi...@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.maison@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.maison@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 <
> > > > > yangpoan@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.maison@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.maison@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
> > > > > > > > > > > > > > >> <js...@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é
> > > > > > >
> > > > >

Re: [DISCUSS] Apache Kafka 4.1.0 release

Posted by Mickael Maison <mi...@gmail.com>.

Hi Andrew,

Feel free to backport to 4.1.

Thanks,
Mickael

On Wed, Jul 2, 2025 at 4:55 PM Andrew Schofield
<an...@outlook.com> wrote:
>
> Hi Mickael,
> We have found an NPE in the group coordinator while stress testing which should probably be fixed.
> There is a chance that a topic being looked up is not present in the metadata image
> in GroupCoordinatorService.onPartitionsDeleted. This is KAFKA-19454.
>
> Here's the trunk PR https://github.com/apache/kafka/pull/20090.
>
> Let me know what you think. We can have a more targeted 4.1 PR ready in moments.
>
> Thanks,
> Andrew
> ________________________________________
> From: Mickael Maison <mi...@gmail.com>
> Sent: 01 July 2025 14:58
> To: dev@kafka.apache.org <de...@kafka.apache.org>
> Subject: Re: [DISCUSS] Apache Kafka 4.1.0 release
>
> Hi,
>
> Quick update on the status of 4.1.0.
>
> We are down to 3 open Jiras:
> - KAFKA-19221: This is fixed in trunk and 4.1. The Jira is just opened
> while the backport to 4.0 is happening.
> - KAFKA-19184: This is a doc update for migrating static to dynamic
> quorums. The PR is under review.
> - KAFKA-19397: We don't have a fix at the moment but people are
> actively working on it.
>
> Thanks,
> Mickael
>
> On Wed, Jun 25, 2025 at 3:41 PM Mickael Maison <mi...@gmail.com> wrote:
> >
> > Hi,
> >
> > Today is code freeze. I've started moving unresolved tickets targeting
> > 4.1.0 to 4.2.0.
> > The only exceptions are for blockers, fixing flaky tests or adding
> > docs for a new feature. For anything else, please ask me before
> > applying it to the 4.1 branch.
> >
> > Thanks,
> > Mickael
> >
> >
> > On Wed, Jun 18, 2025 at 12:14 PM Mickael Maison
> > <mi...@gmail.com> wrote:
> > >
> > > Hi Greg,
> > >
> > > The release plan must match what we ship!
> > > So if KIP-891 has already been merged and is in 4.1, yes it should be
> > > part of the release plan.
> > >
> > > I've added it to the release plan.
> > >
> > > Thanks,
> > > Mickael
> > >
> > > On Tue, Jun 17, 2025 at 6:06 PM Greg Harris
> > > <gr...@aiven.io.invalid> wrote:
> > > >
> > > > 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 <mi...@gmail.com>
> > > > wrote:
> > > >
> > > > > Hi Justine,
> > > > >
> > > > > Ack, thanks for the update.
> > > > >
> > > > > Thanks,
> > > > > Mickael
> > > > >
> > > > > On Thu, Jun 12, 2025 at 6:44 PM Justine Olshan
> > > > > <jo...@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.maison@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
> > > > > > > <js...@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.maison@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 <chia7712@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 <mi...@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.maison@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.maison@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 <
> > > > > yangpoan@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.maison@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.maison@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
> > > > > > > > > > > > > > >> <js...@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é
> > > > > > >
> > > > >

Re: [DISCUSS] Apache Kafka 4.1.0 release

Posted by Andrew Schofield <an...@outlook.com>.

Hi Mickael,
We have found an NPE in the group coordinator while stress testing which should probably be fixed.
There is a chance that a topic being looked up is not present in the metadata image
in GroupCoordinatorService.onPartitionsDeleted. This is KAFKA-19454.

Here's the trunk PR https://github.com/apache/kafka/pull/20090.

Let me know what you think. We can have a more targeted 4.1 PR ready in moments.

Thanks,
Andrew
________________________________________
From: Mickael Maison <mi...@gmail.com>
Sent: 01 July 2025 14:58
To: dev@kafka.apache.org <de...@kafka.apache.org>
Subject: Re: [DISCUSS] Apache Kafka 4.1.0 release

Hi,

Quick update on the status of 4.1.0.

We are down to 3 open Jiras:
- KAFKA-19221: This is fixed in trunk and 4.1. The Jira is just opened
while the backport to 4.0 is happening.
- KAFKA-19184: This is a doc update for migrating static to dynamic
quorums. The PR is under review.
- KAFKA-19397: We don't have a fix at the moment but people are
actively working on it.

Thanks,
Mickael

On Wed, Jun 25, 2025 at 3:41 PM Mickael Maison <mi...@gmail.com> wrote:
>
> Hi,
>
> Today is code freeze. I've started moving unresolved tickets targeting
> 4.1.0 to 4.2.0.
> The only exceptions are for blockers, fixing flaky tests or adding
> docs for a new feature. For anything else, please ask me before
> applying it to the 4.1 branch.
>
> Thanks,
> Mickael
>
>
> On Wed, Jun 18, 2025 at 12:14 PM Mickael Maison
> <mi...@gmail.com> wrote:
> >
> > Hi Greg,
> >
> > The release plan must match what we ship!
> > So if KIP-891 has already been merged and is in 4.1, yes it should be
> > part of the release plan.
> >
> > I've added it to the release plan.
> >
> > Thanks,
> > Mickael
> >
> > On Tue, Jun 17, 2025 at 6:06 PM Greg Harris
> > <gr...@aiven.io.invalid> wrote:
> > >
> > > 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 <mi...@gmail.com>
> > > wrote:
> > >
> > > > Hi Justine,
> > > >
> > > > Ack, thanks for the update.
> > > >
> > > > Thanks,
> > > > Mickael
> > > >
> > > > On Thu, Jun 12, 2025 at 6:44 PM Justine Olshan
> > > > <jo...@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.maison@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
> > > > > > <js...@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.maison@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 <chia7712@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 <mi...@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.maison@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.maison@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 <
> > > > yangpoan@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.maison@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.maison@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
> > > > > > > > > > > > > >> <js...@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é
> > > > > >
> > > >

Re: [DISCUSS] Apache Kafka 4.1.0 release

Posted by Mickael Maison <mi...@gmail.com>.

Hi,

Quick update on the status of 4.1.0.

We are down to 3 open Jiras:
- KAFKA-19221: This is fixed in trunk and 4.1. The Jira is just opened
while the backport to 4.0 is happening.
- KAFKA-19184: This is a doc update for migrating static to dynamic
quorums. The PR is under review.
- KAFKA-19397: We don't have a fix at the moment but people are
actively working on it.

Thanks,
Mickael

On Wed, Jun 25, 2025 at 3:41 PM Mickael Maison <mi...@gmail.com> wrote:
>
> Hi,
>
> Today is code freeze. I've started moving unresolved tickets targeting
> 4.1.0 to 4.2.0.
> The only exceptions are for blockers, fixing flaky tests or adding
> docs for a new feature. For anything else, please ask me before
> applying it to the 4.1 branch.
>
> Thanks,
> Mickael
>
>
> On Wed, Jun 18, 2025 at 12:14 PM Mickael Maison
> <mi...@gmail.com> wrote:
> >
> > Hi Greg,
> >
> > The release plan must match what we ship!
> > So if KIP-891 has already been merged and is in 4.1, yes it should be
> > part of the release plan.
> >
> > I've added it to the release plan.
> >
> > Thanks,
> > Mickael
> >
> > On Tue, Jun 17, 2025 at 6:06 PM Greg Harris
> > <gr...@aiven.io.invalid> wrote:
> > >
> > > 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 <mi...@gmail.com>
> > > wrote:
> > >
> > > > Hi Justine,
> > > >
> > > > Ack, thanks for the update.
> > > >
> > > > Thanks,
> > > > Mickael
> > > >
> > > > On Thu, Jun 12, 2025 at 6:44 PM Justine Olshan
> > > > <jo...@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.maison@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
> > > > > > <js...@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.maison@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 <chia7712@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 <mi...@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.maison@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.maison@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 <
> > > > yangpoan@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.maison@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.maison@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
> > > > > > > > > > > > > >> <js...@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é
> > > > > >
> > > >

Re: [DISCUSS] Apache Kafka 4.1.0 release

Posted by Mickael Maison <mi...@gmail.com>.

Hi,

Today is code freeze. I've started moving unresolved tickets targeting
4.1.0 to 4.2.0.
The only exceptions are for blockers, fixing flaky tests or adding
docs for a new feature. For anything else, please ask me before
applying it to the 4.1 branch.

Thanks,
Mickael


On Wed, Jun 18, 2025 at 12:14 PM Mickael Maison
<mi...@gmail.com> wrote:
>
> Hi Greg,
>
> The release plan must match what we ship!
> So if KIP-891 has already been merged and is in 4.1, yes it should be
> part of the release plan.
>
> I've added it to the release plan.
>
> Thanks,
> Mickael
>
> On Tue, Jun 17, 2025 at 6:06 PM Greg Harris
> <gr...@aiven.io.invalid> wrote:
> >
> > 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 <mi...@gmail.com>
> > wrote:
> >
> > > Hi Justine,
> > >
> > > Ack, thanks for the update.
> > >
> > > Thanks,
> > > Mickael
> > >
> > > On Thu, Jun 12, 2025 at 6:44 PM Justine Olshan
> > > <jo...@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.maison@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
> > > > > <js...@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.maison@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 <chia7712@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 <mi...@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.maison@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.maison@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 <
> > > yangpoan@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.maison@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.maison@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
> > > > > > > > > > > > >> <js...@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é
> > > > >
> > >

Re: [DISCUSS] Apache Kafka 4.1.0 release

Posted by Mickael Maison <mi...@gmail.com>.

Hi Greg,

The release plan must match what we ship!
So if KIP-891 has already been merged and is in 4.1, yes it should be
part of the release plan.

I've added it to the release plan.

Thanks,
Mickael

On Tue, Jun 17, 2025 at 6:06 PM Greg Harris
<gr...@aiven.io.invalid> wrote:
>
> 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 <mi...@gmail.com>
> wrote:
>
> > Hi Justine,
> >
> > Ack, thanks for the update.
> >
> > Thanks,
> > Mickael
> >
> > On Thu, Jun 12, 2025 at 6:44 PM Justine Olshan
> > <jo...@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.maison@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
> > > > <js...@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.maison@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 <chia7712@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 <mi...@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.maison@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.maison@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 <
> > yangpoan@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.maison@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.maison@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
> > > > > > > > > > > >> <js...@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é
> > > >
> >

Re: [DISCUSS] Apache Kafka 4.1.0 release

Posted by Greg Harris <gr...@aiven.io.INVALID>.

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 <mi...@gmail.com>
wrote:

> Hi Justine,
>
> Ack, thanks for the update.
>
> Thanks,
> Mickael
>
> On Thu, Jun 12, 2025 at 6:44 PM Justine Olshan
> <jo...@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.maison@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
> > > <js...@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.maison@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 <chia7712@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 <mi...@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.maison@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.maison@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 <
> yangpoan@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.maison@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.maison@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
> > > > > > > > > > >> <js...@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é
> > >
>

Re: [DISCUSS] Apache Kafka 4.1.0 release

Posted by Mickael Maison <mi...@gmail.com>.

Hi Justine,

Ack, thanks for the update.

Thanks,
Mickael

On Thu, Jun 12, 2025 at 6:44 PM Justine Olshan
<jo...@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 <mi...@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
> > <js...@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 <mi...@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 <ch...@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 <mi...@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.maison@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.maison@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 <ya...@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.maison@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.maison@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
> > > > > > > > > >> <js...@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é
> >

Re: [DISCUSS] Apache Kafka 4.1.0 release

Posted by Justine Olshan <jo...@confluent.io.INVALID>.

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 <mi...@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
> <js...@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 <mi...@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 <ch...@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 <mi...@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.maison@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.maison@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 <ya...@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.maison@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.maison@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
> > > > > > > > >> <js...@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é
>

Re: [DISCUSS] Apache Kafka 4.1.0 release

Posted by Mickael Maison <mi...@gmail.com>.

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
<js...@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 <mi...@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 <ch...@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 <mi...@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 <mi...@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 <mi...@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 <ya...@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.maison@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.maison@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
> > > > > > > >> <js...@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é

Re: [DISCUSS] Apache Kafka 4.1.0 release

Posted by José Armando García Sancio <js...@confluent.io.INVALID>.

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 <mi...@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 <ch...@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 <mi...@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 <mi...@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 <mi...@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 <ya...@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.maison@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.maison@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
> > > > > > >> <js...@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é

Re: [DISCUSS] Apache Kafka 4.1.0 release

Posted by Mickael Maison <mi...@gmail.com>.

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 <ch...@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 <mi...@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 <mi...@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 <mi...@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 <ya...@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.maison@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.maison@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
> > > > > >> <js...@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é
> > > > >
> >

Re: [DISCUSS] Apache Kafka 4.1.0 release

Posted by Chia-Ping Tsai <ch...@gmail.com>.

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 <mi...@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 <mi...@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 <mi...@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 <ya...@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.maison@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.maison@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
> > > > >> <js...@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é
> > > >
>

Re: [DISCUSS] Apache Kafka 4.1.0 release

Posted by Mickael Maison <mi...@gmail.com>.

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 <mi...@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 <mi...@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 <ya...@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 <mi...@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 <mi...@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
> > > >> <js...@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é
> > >

Re: [DISCUSS] Apache Kafka 4.1.0 release

Posted by Mickael Maison <mi...@gmail.com>.

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 <mi...@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 <ya...@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 <mi...@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 <mi...@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
> > >> <js...@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é
> >

Re: [DISCUSS] Apache Kafka 4.1.0 release

Posted by Mickael Maison <mi...@gmail.com>.

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 <ya...@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 <mi...@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 <mi...@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
> >> <js...@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é
>

Re: [DISCUSS] Apache Kafka 4.1.0 release

Posted by PoAn Yang <ya...@gmail.com>.

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 <mi...@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 <mi...@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
>> <js...@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é

Re: [DISCUSS] Apache Kafka 4.1.0 release

Posted by Mickael Maison <mi...@gmail.com>.

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 <mi...@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
> <js...@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é

Re: [DISCUSS] Apache Kafka 4.1.0 release

Posted by Mickael Maison <mi...@gmail.com>.

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
<js...@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é

Re: [DISCUSS] Apache Kafka 4.1.0 release

Posted by José Armando García Sancio <js...@confluent.io.INVALID>.

HI Mickael,

I have added "KIP-1166: Improve high-watermark replication" to the
4.1.0 release wiki page.

Thanks,
-- 
-José