Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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 David Jacot

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

Jira
serverASF JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject = KAFKA AND fixVersion = 3.1.0 AND status not in (resolved, closed) ORDER BY priority DESC, status DESC, updated DESC
serverId5aa69414-a9e9-3523-82ec-879b028fb15b


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.

KIPJIRAComponent
KIP-783: Add TaskId field to StreamsException

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyKAFKA-13381

Streams
KIP-773: Differentiate consistently metric latency measured in millis and nanos

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyKAFKA-13243

Clients
KIP-768: Extend SASL/OAUTHBEARER with Support for OIDC

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyKAFKA-13202

Core/Clients
KIP-766: fetch/findSessions queries with open endpoints for SessionStore/WindowStore

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyKAFKA-13210

Streams
KIP-763: Range queries with open endpoints

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyKAFKA-4064

Streams
KIP-761: Add Total Blocked Time Metric to Streams

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyKAFKA-13229

Streams
KIP-748: Add Broker Count Metrics

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyKAFKA-12882

Core
KIP-690: Add additional configuration to control MirrorMaker 2 internal topics naming convention

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyKAFKA-10777

MirrorMaker
KIP-633: Deprecate 24-hour Default Grace Period for Windowed Operations in Streams

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyKAFKA-8613
/
Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyKAFKA-12909

Streams


Postponed to subsequent release

KIPJIRAComponent
KIP-775: Custom partitioners in foreign key joins

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyKAFKA-13261

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

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyKAFKA-12473

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

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyKAFKA-13043

Clients
KIP-708: Rack awareness for Kafka Streams

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyKAFKA-6718

Streams
KIP-698: Add Explicit User Initialization of Broker-side State to Kafka Streams

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyKAFKA-10357

Streams
KIP-691: Enhance Transactional Producer Exception Handling

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyKAFKA-10733

Clients
KIP-627: Expose Trogdor-specific JMX Metrics for Tasks and Agents

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyKAFKA-8528

Trogdor
KIP-618: Exactly-Once Support for Source Connectors

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyKAFKA-10000
/
Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyKAFKA-6080

Connect
KIP-653: Upgrade log4j to log4j2

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyKAFKA-9366

Clients, Connect, Core, Streams
KIP-405: Kafka Tiered Storage

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyKAFKA-7739

Core
KIP-390: Support Compression Level

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyKAFKA-7632

Core, Clients