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 <mickael.mai...@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 <mickael.mai...@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 <chia7...@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 > > > > > <mickael.mai...@gmail.com> wrote: > > > > > > > > > > > > Hi PoAn, > > > > > > > > > > > > Since both KIPs were accepted before the deadline I've added them to > > > > > > the release plan. In the future feel free to edit the release plan > > > > > > yourself. > > > > > > > > > > > > Note that feature freeze is this week, so the goal is to merge all > > > > > > KIP-related code by the end of the week. If that's not possible let > > > > > > me > > > > > > know. > > > > > > > > > > > > Thanks, > > > > > > Mickael > > > > > > > > > > > > > > > > > > > > > > > > On Mon, Jun 2, 2025 at 9:14 AM PoAn Yang <yangp...@gmail.com> wrote: > > > > > > > > > > > > > > Hi Mickael, > > > > > > > > > > > > > > May I add KIP-1101 (https://cwiki.apache.org/confluence/x/FouMEw) > > > > > > > and > > > > > > > KIP-1142 (https://cwiki.apache.org/confluence/x/AAqWF) to > > > > > > > release plan? > > > > > > > These KIPs were accepted on April 17th and April 29th. I’m sorry > > > > > > > for not > > > > > > > adding them to the release plan when they were accepted. > > > > > > > > > > > > > > For KIP-1101, we already merged consumer group PRs. Remaining PRs > > > > > > > are for share / stream groups and one for integration test. > > > > > > > They’re all ready > > > > > > > for reviewing: > > > > > > > * https://github.com/apache/kafka/pull/19802 > > > > > > > * https://github.com/apache/kafka/pull/19796 > > > > > > > * https://github.com/apache/kafka/pull/19856 > > > > > > > > > > > > > > For KIP-1142, it's almost finished. One remaining PR is about > > > > > > > compatibility > > > > > > > of missing metric. > > > > > > > * https://github.com/apache/kafka/pull/19877 > > > > > > > > > > > > > > Thanks, > > > > > > > PoAn > > > > > > > > > > > > > > > > > > > > > > On May 14, 2025, at 6:20 PM, Mickael Maison > > > > > > > > <mickael.mai...@gmail.com> wrote: > > > > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > > > Reminder that today is KIP freeze. > > > > > > > > If you have a KIP that has been approved before the end of the > > > > > > > > day, > > > > > > > > you can add it to the 4.1.0 release plan. > > > > > > > > > > > > > > > > The next milestone is feature freeze on June 4. > > > > > > > > > > > > > > > > Thanks, > > > > > > > > Mickael > > > > > > > > > > > > > > > > On Tue, May 13, 2025 at 6:48 PM Mickael Maison > > > > > > > > <mickael.mai...@gmail.com> wrote: > > > > > > > >> > > > > > > > >> Hi Kirk, > > > > > > > >> Yes it was approved before KIP freeze, so feel free to add it > > > > > > > >> to the > > > > > > > >> release plan. (I would have done it now but the wiki seems to > > > > > > > >> be down > > > > > > > >> at the moment) > > > > > > > >> > > > > > > > >> Hi Jose, > > > > > > > >> Ack > > > > > > > >> > > > > > > > >> Thanks, > > > > > > > >> Mickael > > > > > > > >> > > > > > > > >> On Tue, May 13, 2025 at 6:17 PM José Armando García Sancio > > > > > > > >> <jsan...@confluent.io.invalid> wrote: > > > > > > > >>> > > > > > > > >>> HI Mickael, > > > > > > > >>> > > > > > > > >>> I have added "KIP-1166: Improve high-watermark replication" > > > > > > > >>> to the > > > > > > > >>> 4.1.0 release wiki page. > > > > > > > >>> > > > > > > > >>> Thanks, > > > > > > > >>> -- > > > > > > > >>> -José > > > > > > > > > > > > > > > >
