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

Compare with Current View Page History

« Previous Version 29 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 (new date):  (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 (new date): 
  • 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 Konstantine Karantasis

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 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.

KIPJIRAComponent
KIP-751: Drop support for Scala 2.12 in Kafka 4.0 (deprecate in 3.0)

Unable to render Jira issues macro, execution error.

Documentation
KIP-750: Drop support for Java 8 in Kafka 4.0 (deprecate in 3.0)

Unable to render Jira issues macro, execution error.

Documentation
KIP-746: Revise KRaft Metadata Records

Unable to render Jira issues macro, execution error.

Core
KIP-745: Connect API to restart connector and tasks

Unable to render Jira issues macro, execution error.

Connect
KIP-744: Migrate TaskMetadata and ThreadMetadata to an interface with internal implementation

Unable to render Jira issues macro, execution error.

Streams
KIP-743: Remove config value 0.10.0-2.4 of Streams built-in metrics version config

Unable to render Jira issues macro, execution error.

Streams
KIP-741: Change default serde to be null

Unable to render Jira issues macro, execution error.

Streams
KIP-740: Clean up public API in TaskId and fix TaskMetadata#taskId()

Unable to render Jira issues macro, execution error.

Streams
KIP-738: Removal of Connect's internal converter properties

Unable to render Jira issues macro, execution error.

Connect
KIP-734: Improve AdminClient.listOffsets to return timestamp and offset for the record with the largest timestamp

Unable to render Jira issues macro, execution error.

Clients
KIP-733: change Kafka Streams default replication factor config

Unable to render Jira issues macro, execution error.

Streams
KIP-732: Deprecate eos-alpha and replace eos-beta with eos-v2

Unable to render Jira issues macro, execution error.

Streams
KIP-730: Producer ID generation in KRaft mode

Unable to render Jira issues macro, execution error.

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

Unable to render Jira issues macro, execution error.

Clients
KIP-725: Streamlining configurations for WindowedSerializer and WindowedDeserializer.

Unable to render Jira issues macro, execution error.

Streams
KIP-724: Drop support for message formats v0 and v1

Unable to render Jira issues macro, execution error.

Core, Clients
KIP-722: Enable connector client overrides by default

Unable to render Jira issues macro, execution error.

Connect
KIP-721: Enable connector log contexts in Connect Log4j configuration

Unable to render Jira issues macro, execution error.

Connect
KIP-720: Deprecate MirrorMaker v1

Unable to render Jira issues macro, execution error.

Core
KIP-716: Allow configuring the location of the offset-syncs topic with MirrorMaker2

Unable to render Jira issues macro, execution error.

MirrorMaker
KIP-715: Expose Committed offset in streams

Unable to render Jira issues macro, execution error.

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

Unable to render Jira issues macro, execution error.

Core, Clients
KIP-708: Rack awareness for Kafka Streams

Unable to render Jira issues macro, execution error.

Streams
KIP-707: The future of KafkaFuture

Unable to render Jira issues macro, execution error.

Clients

KIP-699: Update FindCoordinator to resolve multiple Coordinators at a time

Unable to render Jira issues macro, execution error.

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

Unable to render Jira issues macro, execution error.

Streams
KIP-695: Further Improve Kafka Streams Timestamp Synchronization Unable to render Jira issues macro, execution error. Streams
KIP-691: Enhance Transactional Producer Exception Handling

Unable to render Jira issues macro, execution error.

Clients
KIP-679: Producer will enable the strongest delivery guarantee by default

Unable to render Jira issues macro, execution error.

Clients
KIP-666: Add Instant-based methods to ReadOnlySessionStore

Unable to render Jira issues macro, execution error.

Streams
KIP-653: Upgrade log4j to log4j2

Unable to render Jira issues macro, execution error.

Applies to almost all the components
KIP-633: Drop 24 hour default of grace period in Streams

Unable to render Jira issues macro, execution error.

Streams
KIP-623: Add "internal-topics" option to streams application reset tool

Unable to render Jira issues macro, execution error.

Streams, Tools
KIP-622: Add currentSystemTimeMs and currentStreamTimeMs to ProcessorContext

Unable to render Jira issues macro, execution error.

Streams
KIP-466: Add support for List<T> serialization and deserialization

Unable to render Jira issues macro, execution error.

Clients, Streams
KIP-405: Kafka Tiered Storage

Unable to render Jira issues macro, execution error.

Core
KIP-390: Support Compression Level

Unable to render Jira issues macro, execution error.

Clients


Postponed to subsequent release

No KIPs in this category currently. 


  • No labels