Great, thanks!

On Mon, Feb 2, 2026 at 12:33 PM Christo Lolov <[email protected]> wrote:
>
> Hello!
>
> The DLQ issue has been resolved and cherry-picked on 4.2.
>
> Mickael, I cherry-picked KAFKA-19571 as well!
>
> I am now closing this vote and will shortly be raising the next RC.
>
> Best,
> Christo
>
> On Fri, 30 Jan 2026 at 17:27, Mickael Maison <[email protected]>
> wrote:
>
> > Hi Christo,
> >
> > If there's another RC, can we cherry pick
> > https://issues.apache.org/jira/browse/KAFKA-19571?
> >
> > It's already backported to 4.1, and I'll backport to 4.0 next week.
> >
> > Thanks,
> > Mickael
> >
> > On Thu, Jan 29, 2026 at 6:21 PM Bill Bejeck <[email protected]> wrote:
> > >
> > > Hi Chia-Ping,
> > >
> > > Yes, you are correct, my mistake. We should get this in.
> > >
> > > Thanks,
> > > Bill
> > >
> > > On Thu, Jan 29, 2026 at 11:39 AM Chia-Ping Tsai <[email protected]>
> > wrote:
> > >
> > > > Thanks for the feedback, Bill.
> > > >
> > > > Actually, I double-checked KAFKA-16505, and it appears this feature
> > > > (KIP-1034) is new in 4.2.0.
> > > >
> > > > Please correct me if I misunderstood.
> > > >
> > > > Best,
> > > >
> > > > Chia-Ping
> > > >
> > > > Bill Bejeck <[email protected]> 於 2026年1月30日週五 上午12:19寫道:
> > > >
> > > > > Hi Chia-Ping,
> > > > >
> > > > > Thanks for mentioning this.  Since this commit was in the previous
> > > > release
> > > > > and not a regression, I'm not sure that it meets the bar for a
> > blocker.
> > > > > But I don't have a strong opinion, so I'll leave it to Christo to
> > decide.
> > > > >
> > > > > Regards,
> > > > > Bill
> > > > >
> > > > > On Thu, Jan 29, 2026 at 7:57 AM Chia-Ping Tsai <[email protected]>
> > > > > wrote:
> > > > >
> > > > > > hi Christo
> > > > > >
> > > > > > I have spotted a potential blocker, and a patch will be ready soon
> > > > > >
> > > > > > https://github.com/apache/kafka/pull/17942#discussion_r2737868443
> > > > > >
> > > > > > Best,
> > > > > > Chia-Ping
> > > > > >
> > > > > > On 2026/01/27 15:50:25 Christo Lolov wrote:
> > > > > > > Hello Kafka users, developers and client-developers,
> > > > > > >
> > > > > > > This is the RC2 candidate for release of Apache Kafka 4.2.0.
> > > > > > >
> > > > > > > This release has many exciting changes:
> > > > > > > * Kafka Queues (Share Groups) is now production-ready with new
> > > > > > > features like the RENEW acknowledgement type for extended
> > processing
> > > > > > > times, adaptive batching for coordinators, and comprehensive lag
> > > > > > > metrics.
> > > > > > > * Kafka Streams brings the server-side rebalance protocol to GA
> > with
> > > > a
> > > > > > > limited feature set, adds dead letter queue support in exception
> > > > > > > handlers, introduces anchored wall-clock punctuation for
> > > > deterministic
> > > > > > > scheduling, and gives users full control over whether to send a
> > leave
> > > > > > > group request on closing.
> > > > > > > * This release also delivers significant improvements to
> > consistency
> > > > > > > and observability: CLI tools now feature standardized arguments
> > like
> > > > > > > --bootstrap-server across all tools, metric naming has been
> > corrected
> > > > > > > to follow the kafka.COMPONENT convention, and new idle ratio
> > metrics
> > > > > > > provide better visibility into controller and MetadataLoader
> > > > > > > performance.
> > > > > > > * Security is enhanced with a new allowlist connector client
> > > > > > > configuration override policy, while thread-safety improvements
> > to
> > > > > > > RecordHeader eliminate concurrency risks.
> > > > > > > * Additional highlights include external schema support in
> > > > > > > JsonConverter for reduced message sizes, dynamic configuration
> > for
> > > > > > > remote log manager thread pools, and rack ID exposure in the
> > Admin
> > > > API
> > > > > > > for consumer and share group members.
> > > > > > >
> > > > > > > Release notes for the 4.2.0 release:
> > > > > > >
> > > > > >
> > > > >
> > > >
> > https://dist.apache.org/repos/dist/dev/kafka/4.2.0-rc2/RELEASE_NOTES.html
> > > > > > >
> > > > > > > *** Please download, test and vote by Friday, January 30, 5pm UTC
> > > > > > >
> > > > > > > Kafka's KEYS file containing PGP keys we use to sign the release:
> > > > > > > https://kafka.apache.org/KEYS
> > > > > > >
> > > > > > > * Release artifacts to be voted upon (source and binary):
> > > > > > > https://dist.apache.org/repos/dist/dev/kafka/4.2.0-rc2/
> > > > > > >
> > > > > > > * Docker release artifacts to be voted upon:
> > > > > > > apache/kafka:4.2.0-rc2
> > > > > > > apache/kafka-native:4.2.0-rc2
> > > > > > >
> > > > > > > * Maven artifacts to be voted upon:
> > > > > > >
> > > > https://repository.apache.org/content/groups/staging/org/apache/kafka/
> > > > > > >
> > > > > > > * Javadoc:
> > > > > > >
> > > > > >
> > > > >
> > > >
> > https://dist.apache.org/repos/dist/dev/kafka/4.2.0-rc2/javadoc/index.html
> > > > > > >
> > > > > > > * Tag to be voted upon (off 4.2 branch) is the 4.2.0 tag:
> > > > > > > https://github.com/apache/kafka/releases/tag/4.2.0-rc2
> > > > > > >
> > > > > > > * Documentation:
> > > > > > > * Protocol:
> > > > > > > https://github.com/apache/kafka-site/pull/785
> > > > > > >
> > > > > > > * Successful CI builds for the 4.2 branch:
> > > > > > > Unit/integration tests: The ongoing build for the 4.2.0-rc2 tag
> > can
> > > > be
> > > > > > found
> > > > > > > at
> > > > > >
> > > >
> > https://github.com/apache/kafka/actions/runs/21398201956/job/61611167690
> > > > > > >
> > > > > > > System tests: I have started the tests in my environment and will
> > > > share
> > > > > > test
> > > > > > > results in the next ~24 hours.
> > > > > > >
> > > > > > > * Successful Docker Image Github Actions Pipeline for 4.2 branch:
> > > > > > > Docker Build Test Pipeline (JVM):
> > > > > > > https://github.com/apache/kafka/actions/runs/21402423697
> > > > > > > Docker Build Test Pipeline (Native):
> > > > > > > https://github.com/apache/kafka/actions/runs/21398799585
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Christo
> > > > > > >
> > > > > >
> > > > >
> > > >
> >

Reply via email to