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

Compare with Current View Page History

« Previous Version 28 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 Mickael Maison 

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 the 3.5.0 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-405: Kafka Tiered Storage

Unable to render Jira issues macro, execution error.

coreWIP
KIP-581: Value of optional null field which has default value

Unable to render Jira issues macro, execution error.

connectDone
KIP-641 An new java interface to replace 'kafka.common.MessageReader'

Unable to render Jira issues macro, execution error.

tool/clientDone
KIP-710: Full support for distributed mode in dedicated MirrorMaker 2.0 clusters

Unable to render Jira issues macro, execution error.

connectDone
KIP-813: Shareable State Stores

Unable to render Jira issues macro, execution error.

StreamsPR available
KIP-847: Add ProducerIdCount metrics

Unable to render Jira issues macro, execution error.

coreDone
KIP-863: Reduce Fetcher#parseRecord() memory copy

Unable to render Jira issues macro, execution error.

clientsPR available
KIP-875: First-class offsets support in Kafka Connect

Unable to render Jira issues macro, execution error.

connectWIP
KIP-884: Add config to configure KafkaClientSupplier in Kafka Streams

Unable to render Jira issues macro, execution error.

StreamsDone
KIP-887: Add ConfigProvider to make use of environment variables

Unable to render Jira issues macro, execution error.

clientsDone
KIP-889: Versioned State Stores

Unable to render Jira issues macro, execution error.

StreamsDone
KIP-893: The Kafka protocol should support nullable structs

Unable to render Jira issues macro, execution error.

coreDone
KIP-894: Use incrementalAlterConfig for syncing topic configurations 

Unable to render Jira issues macro, execution error.

connectDone
KIP-900: KRaft kafka-storage.sh API additions to support SCRAM for Kafka Brokers

Unable to render Jira issues macro, execution error.

coreDone

KIP-904: Kafka Streams - Guarantee subtractor is called before adder if key has not changed

Unable to render Jira issues macro, execution error.

StreamsDone (system test missing)
KIP-907: Add Boolean Serde to public interface

Unable to render Jira issues macro, execution error.

StreamsDone (only docs missing)
KIP-911: Add source tag to Mirror source metric

Unable to render Jira issues macro, execution error.

connectDone
KIP-914: DSL Processor Semantics for Versioned Stores

Unable to render Jira issues macro, execution error.

StreamsWIP

KIP-915: Txn and Group Coordinator Downgrade Foundation

Unable to render Jira issues macro, execution error.

coreWIP


Postponed to subsequent release

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

Unable to render Jira issues macro, execution error.

KIP-770: Replace "buffered.records.per.partition" with "input.buffer.max.bytes"

Unable to render Jira issues macro, execution error.

KIP-797: Accept duplicate listener on port for IPv4/IPv6

Unable to render Jira issues macro, execution error.

KIP-821: Connect Transforms support for nested structures

Unable to render Jira issues macro, execution error.

KIP-866 ZooKeeper to KRaft Migration

Unable to render Jira issues macro, execution error.

KIP-903: Replicas with stale broker epoch should not be allowed to join the ISR

Unable to render Jira issues macro, execution error.

  • No labels