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

Posted to dev@kafka.apache.org by "Chris Egerton (Jira)" <ji...@apache.org> on 2024/05/08 13:06:00 UTC

[jira] [Resolved] (KAFKA-16108) Backport fix for KAFKA-16093 to 3.7

     [ https://issues.apache.org/jira/browse/KAFKA-16108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Egerton resolved KAFKA-16108.
-----------------------------------
    Resolution: Done

> Backport fix for KAFKA-16093 to 3.7
> -----------------------------------
>
>                 Key: KAFKA-16108
>                 URL: https://issues.apache.org/jira/browse/KAFKA-16108
>             Project: Kafka
>          Issue Type: Improvement
>          Components: connect
>            Reporter: Chris Egerton
>            Assignee: Chris Egerton
>            Priority: Blocker
>             Fix For: 3.7.1
>
>
> A fix for KAFKA-16093 is present on the branches trunk (the version for which is currently 3.8.0-SNAPSHOT) and 3.6. We are in code freeze for the 3.7.0 release, and this issue is not a blocker, so it cannot be backported right now.
> We should backport the fix once 3.7.0 has been released and before 3.7.1 is released.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)