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 no
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 th
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
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/
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
>
> > On Wed, Jul 2, 2025 at 5:19 PM Andrew Schofield <
> > andrew_schofield_j...@outlook.com> wrote:
> >
> > > Thanks. PR merged into 4.1.
> > >
> > > Andrew
> > >
> > >
> > > F
___
> > From: Mickael Maison
> > Sent: 02 July 2025 16:29
> > To: dev@kafka.apache.org
> > Subject: Re: [DISCUSS] Apache Kafka 4.1.0 release
> >
> > Hi Andrew,
> >
> > Feel free to backport to 4.1.
> >
> > Thanks,
> > Mic
erged into 4.1.
>
> Andrew
>
>
> From: Mickael Maison
> Sent: 02 July 2025 16:29
> To: dev@kafka.apache.org
> Subject: Re: [DISCUSS] Apache Kafka 4.1.0 release
>
> Hi Andrew,
>
> Feel free to backport to 4.1.
>
> Tha
Thanks. PR merged into 4.1.
Andrew
From: Mickael Maison
Sent: 02 July 2025 16:29
To: dev@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
dy in
> moments.
>
> Thanks,
> Andrew
>
> From: Mickael Maison
> Sent: 01 July 2025 14:58
> To: dev@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
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
Sent: 01 July 2025 14:58
To: dev@kafka.apache.org
Subject: Re: [DISCUSS] Apache Kafka 4.1.0 releas
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:
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
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
wrote:
>
> Hi Mickael,
>
> KIP-891 [1] is/was merged
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/di
Hi Justine,
Ack, thanks for the update.
Thanks,
Mickael
On Thu, Jun 12, 2025 at 6:44 PM Justine Olshan
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
> relative
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:
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
wrote:
>
> Hi Mi
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 1
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
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 wrote:
>
> Hi,
>
> We are now past feature freeze.
> My plan was to cut t
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 於 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
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,
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
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
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 wrote:
>
> Hi Kirk,
> Yes it was a
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
wrote:
>
> HI Mickael,
>
> I have added "KIP
HI Mickael,
I have added "KIP-1166: Improve high-watermark replication" to the
4.1.0 release wiki page.
Thanks,
--
-José
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
+1 to Matthias' comment about fixed dates.
Given that the release schedule has a fixed cadence, there shouldn't need to be
much discussion around dates for each release.
Kirk
On Thu, Apr 17, 2025, at 2:54 PM, Matthias J. Sax wrote:
> Thanks!
>
> I am wondering if we should set more or less "f
Thanks!
I am wondering if we should set more or less "fixed" dates (or date
ranges) for future release? To keep a real "time based" release schedule
and give some guidance?
Thoughts?
-Matthias
On 4/17/25 11:55 AM, Ismael Juma wrote:
Awesome, thanks.
Ismael
On Thu, Apr 17, 2025, 12:10 A
Awesome, thanks.
Ismael
On Thu, Apr 17, 2025, 12:10 AM Mickael Maison
wrote:
> Hi,
>
> I updated the release plan and moved all dates forward by 2 weeks.
>
> Thanks,
> Mickael
>
> On Thu, Apr 17, 2025 at 3:19 AM Matthias J. Sax wrote:
> >
> > I would want to backup the idea to move the release
Hi,
I updated the release plan and moved all dates forward by 2 weeks.
Thanks,
Mickael
On Thu, Apr 17, 2025 at 3:19 AM Matthias J. Sax wrote:
>
> I would want to backup the idea to move the release earlier if possible.
> Looking into historic release dates, we are slipping by roughly two
> week
I would want to backup the idea to move the release earlier if possible.
Looking into historic release dates, we are slipping by roughly two
weeks year over year, and I think it would be good to work against it.
4.0.0: March/18 2025
3.7.0: Feb/27 2024
3.4.0: Feb/7 2023
3.1.0: Jan/24 2022
It's
The issue is that July 23rd is the "earliest release date" but historically
the actual release is weeks after that date from the release plan. So, a
code freeze of June 25th would probably give us a better chance of hitting
the 4 months goal. Would that work for you?
Thanks,
Ismael
On Wed, Apr 16
Hi Ismael,
Sorry I had written the reply but never hit "send".
France has a public holiday on July 14, so I thought I may be out some
days that week. To be safe, I picked the week after as I thought July
23 was close enough to mid July.
That said I currently don't have anything planned, so I can
Hi Mickael,
Thoughts on my message below?
Ismael
On Thu, Apr 10, 2025, 7:46 AM Ismael Juma wrote:
> Hi Mickael,
>
> The release plan indicates a release in August. However, 4.0 was released
> on March 18. If we stick to the 4 months schedule, the target release
> should be mid July. Is there a
+1.
Thanks, Mickael!
Colin
On Wed, Mar 19, 2025, at 04:58, 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
Hi Mickael,
The release plan indicates a release in August. However, 4.0 was released
on March 18. If we stick to the 4 months schedule, the target release
should be mid July. Is there a reason why we didn't set the freeze dates
earlier in order to enable that?
Ismael
On Wed, Apr 2, 2025 at 10:3
+1 thanks Mickael!
David Arthur
On Wed, Mar 19, 2025 at 07:59 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
Hi,
You can find the release plan in the wiki:
https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+4.1.0
Thanks,
Mickael
On Fri, Mar 21, 2025 at 8:15 PM José Armando García Sancio
wrote:
>
> Thanks Mickael.
>
> On Wed, Mar 19, 2025 at 9:20 AM Ismael Juma wrote:
> >
> > Thanks Micka
Thanks Mickael.
On Wed, Mar 19, 2025 at 9:20 AM Ismael Juma wrote:
>
> Thanks Mickael!
>
> Ismael
>
> On Wed, Mar 19, 2025, 5:54 AM David Arthur wrote:
>
> > +1 thanks Mickael!
> >
> > David Arthur
> >
> >
> > On Wed, Mar 19, 2025 at 07:59 Mickael Maison
> > wrote:
> >
> > > Hi,
> > >
> > > I'd
Thanks Mickael!
Ismael
On Wed, Mar 19, 2025, 5:54 AM David Arthur wrote:
> +1 thanks Mickael!
>
> David Arthur
>
>
> On Wed, Mar 19, 2025 at 07:59 Mickael Maison
> wrote:
>
> > Hi,
> >
> > I'd like to volunteer to be the release manager for the Apache Kafka
> > 4.1.0 release.
> >
> > If there
Thanks to Mickael for taking this over!!!
Best,
Chia-Ping
On 2025/03/19 11:58:37 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.
>
44 matches
Mail list logo
