You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 22 Next »

Release Dates

  • KIP Freeze:  (A KIP must be accepted by this date in order to be considered for this release. Note, any KIP that may not be implemented in a week, or that might destabilize the release, should be deferred.)
  • Feature Freeze:  (major features merged & working on stabilization, minor features have PR, release branch cut; anything not in this state will be automatically moved to the next release in JIRA)
  • Code Freeze:
  • At least two weeks of stabilization will follow Code Freeze.


These dates are goals and subject to change, but we expect to stay on the Time Based Release Plan unless unexpected critical issues come up. While the earliest possible release date is 2w after code freeze, release candidates (RCs) will roll out as needed until the release vote passes.

The release manager is Jose Armando Garcia Sancio 

How to Contribute

Before code freeze:

  • Participate in votes and discussions to land or postpone the open KIPs.
  • Review patches. We anticipate that this release, as it usually happens, will be bottlenecked mostly on reviews. The more reviewers, the more content we can fit in.
  • Write unit/integration/system tests. We want to preserve the tradition of high-quality releases in Apache Kafka. 

After code freeze:

  • Write more unit/integration/system testsWe want to preserve the tradition of high-quality releases in Apache Kafka.
  • Improve documentation.
  • Test the release candidates. 
  • Open blocker JIRAs on critical issues found. Open non-blocker JIRAs on any other issues found.
  • Fix critical bugs.
  • Review bug fixes.
  • Vote on release candidates. Even though only PMC votes are binding, community votes are super important as we evaluate the readiness of the release.

Open Issues

key summary type created updated due assignee reporter customfield_12311032 customfield_12311037 customfield_12311022 customfield_12311027 priority status resolution

JQL and issue key arguments for this macro require at least one Jira application link to be configured


Also feel free to refer to this release page for more details of the included tickets (requires log in to the Apache Kafka Jira project).

Planned KIP Content

Note: The planned content is not binding - final content will be based the features committed by branch-cutting date. See Kafka Improvement Proposals for the full list of KIPs.

KIPJIRAComponentStatus
KIP-851: Add requireStable flag into ListConsumerGroupOffsetsOptions

N/A

ClientDone
KIP-846: Source/sink node metrics for Consumed/Produced throughput in Streams

Unable to render Jira issues macro, execution error.

StreamsDone
KIP-843: Adding addMetricIfAbsent method to Metrics

Unable to render Jira issues macro, execution error.

ClientDone
KIP-841: Fenced replicas should not be allowed to join the ISR in KRaft

Unable to render Jira issues macro, execution error.

CoreDone
KIP-835: Monitor KRaft Controller Quorum Health

Unable to render Jira issues macro, execution error.

CoreDone
KIP-834: Pause / Resume KafkaStreams Topologies

Unable to render Jira issues macro, execution error.

StreamsDone
KIP-833: Mark KRaft as Production Ready
CoreDone
KIP-831: Add metric for log recovery progress

Unable to render Jira issues macro, execution error.

CoreDone
KIP-827: Expose logdirs total and usable space via Kafka API

Unable to render Jira issues macro, execution error.

CoreDone
KIP-824: Allowing dumping segmentlogs limiting the batches in the output

Unable to render Jira issues macro, execution error.

ToolDone
KIP-820: Extend KStream process with new Processor API

Unable to render Jira issues macro, execution error.

StreamsDone
KIP-812: Introduce another form of the `KafkaStreams.close()` API that forces the member to leave the consumer group

Unable to render Jira issues macro, execution error.

StreamsDone
KIP-778: KRaft Upgrades

Unable to render Jira issues macro, execution error.

CoreTBD
KIP-726: Make the "cooperative-sticky, range" as the default assignor

Unable to render Jira issues macro, execution error.


TBD
KIP-709: Extend OffsetFetch requests to accept multiple group ids.

Unable to render Jira issues macro, execution error.


Done. Remove the WIP from the parent page.
KIP-618: Exactly-Once Support for Source Connectors

Unable to render Jira issues macro, execution error.


Done
KIP-373: Allow users to create delegation tokens for other users

Unable to render Jira issues macro, execution error.


Done.

The KIPs parent page says 2.7.0.


Postponed to subsequent release

  1. KIP-405: Kafka Tiered Storage
  2. KIP-792: Add "generation" field into consumer protocol
  3. KIP-796: Interactive Query v2
  4. KIP-797: Accept duplicate listener on port for IPv4/IPv6
  • No labels