[
https://issues.apache.org/jira/browse/KAFKA-16337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-16337:
------------------------------------
Description:
h1. *THIS TICKET CANNOT BE WORKED ON, UNTIL WE DO APACHE KAFKA 5.0 RELEASE.*
This is an umbrella ticket that tries to collect all APIs under Kafka Streams
that were deprecated in 3.6 or later. When the release scheduled for 5.0 will
be set, we might need to remove sub-tasks if they don't hit the 1-year
threshold.
Each subtask will de focusing on a specific API, so it's easy to discuss if it
should be removed by 5.0.0 or maybe even at a later point.
was:
This is an umbrella ticket that tries to collect all APIs under Kafka Streams
that were deprecated in 3.6 or later. When the release scheduled for 5.0 will
be set, we might need to remove sub-tasks if they don't hit the 1-year
threshold.
Each subtask will de focusing on a specific API, so it's easy to discuss if it
should be removed by 5.0.0 or maybe even at a later point.
> Remove Deprecates APIs of Kafka Streams in 5.0
> ----------------------------------------------
>
> Key: KAFKA-16337
> URL: https://issues.apache.org/jira/browse/KAFKA-16337
> Project: Kafka
> Issue Type: Task
> Components: streams, streams-test-utils
> Affects Versions: 5.0.0
> Reporter: Matthias J. Sax
> Priority: Blocker
> Fix For: 5.0.0
>
>
> h1. *THIS TICKET CANNOT BE WORKED ON, UNTIL WE DO APACHE KAFKA 5.0 RELEASE.*
> This is an umbrella ticket that tries to collect all APIs under Kafka Streams
> that were deprecated in 3.6 or later. When the release scheduled for 5.0 will
> be set, we might need to remove sub-tasks if they don't hit the 1-year
> threshold.
> Each subtask will de focusing on a specific API, so it's easy to discuss if
> it should be removed by 5.0.0 or maybe even at a later point.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
