Release Dates
- KIP Freeze: 26th July 23 (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: 16th Aug (major features merged & working on stabilisation, minor features have PR, release branch cut; anything not in this state will be automatically moved to the next release in JIRA)
- Code Freeze: 30th Aug 23
- At least two weeks of stabilisation 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 Satish Duggana
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 tests. We 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.
- Ensure that release candidates include artifacts for the new Connect test-plugins module (see KAFKA-15249 - Getting issue details... STATUS )
Open Issues
Also feel free to refer to the 3.6.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.
| KIP | JIRA | Component | Status |
|---|---|---|---|
| KIP-405: Kafka Tiered Storage | KAFKA-7739 - Getting issue details... STATUS | core | Majority is completed. Remaining to be done in 3.7.0 |
| KIP-793: Allow sink connectors to be used with topic-mutating SMTs | KAFKA-13431 - Getting issue details... STATUS | connect | Completed |
| KIP-797: Accept duplicate listener on port for IPv4/IPv6 | KAFKA-13299 - Getting issue details... STATUS | core | Completed |
| KIP-868 Metadata Transactions | KAFKA-14305 - Getting issue details... STATUS | core | Completed |
| KIP-875: First-class offsets support in Kafka Connect | KAFKA-4107 - Getting issue details... STATUS | connect | Completed In prior releases: connector STOPPED state, offsets read API In this release: Offsets alter and reset APIs |
| KIP-890: Transactions Server-Side Defense | KAFKA-14402 - Getting issue details... STATUS | core | Part 1 Completed |
| KIP-898: Modernize Connect plugin discovery | KAFKA-14627 - Getting issue details... STATUS | connect | Completed |
| KIP-902: Upgrade Zookeeper to 3.8.2 | KAFKA-14661 - Getting issue details... STATUS | core | Completed |
KAFKA-15107 - Getting issue details... STATUS | core | Completed | |
KAFKA-14936 - Getting issue details... STATUS | streams | KIP Accepted Implementation seems to be completed but yet to be confirmed by author. | |
KAFKA-15022 - Getting issue details... STATUS | streams | Partially implemented in 3.6 | |
| KIP-937: Improve Message Timestamp Validation | KAFKA-14991 - Getting issue details... STATUS | core | Completed |
| KIP-938: Add more metrics for measuring KRaft performance | KAFKA-15183 - Getting issue details... STATUS | core | KIP Accepted Majority is completed. Remaining to be done in 3.7.0 |
KAFKA-14944 - Getting issue details... STATUS | clients | Completed | |
KAFKA-15245 - Getting issue details... STATUS | core | Completed | |
KIP-941: Range queries to accept null lower and upper bounds | KAFKA-15126 - Getting issue details... STATUS | streams | Completed |
Postponed to subsequent release
| KIP | JIRA | Component | Status |
|---|---|---|---|
| KIP-580: Exponential Backoff for Kafka Clients | KAFKA-9800 - Getting issue details... STATUS | clients | Implemented Plan to release it in 3.7.0 |
| KIP-726: Make the "cooperative-sticky, range" as the default assignor | KAFKA-12473 - Getting issue details... STATUS | clients | KIP Accepted Implementation not yet completed |
| KIP-770: Replace "buffered.records.per.partition" with "input.buffer.max.bytes" | KAFKA-13152 - Getting issue details... STATUS | streams | KIP Accepted Implementation in progress, not yet reviewed. |
| KIP-813: Shareable State Stores | KAFKA-10892 - Getting issue details... STATUS | streams | KIP Accepted Implementation not yet completed. |
| KIP-821: Connect Transforms support for nested structures | KAFKA-13656 - Getting issue details... STATUS | connect | KIP Accepted Implementation in progress |
| KIP-852: Optimize calculation of size for log in remote tier | KAFKA-14038 - Getting issue details... STATUS | core | KIP Accepted Partially completed |
KAFKA-15230 - Getting issue details... STATUS | core | KIP Accepted Not yet completed | |
KAFKA-15022 - Getting issue details... STATUS | streams | Partially implemented in 3.6 | |
| KIP-938: Add more metrics for measuring KRaft performance | KAFKA-15183 - Getting issue details... STATUS | core | KIP Accepted Majority is completed. Remaining to be done in 3.7.0 |
KIP-872: Add Serializer#serializeToByteBuffer() to reduce memory copying | KAFKA-14945 - Getting issue details... STATUS | clients | KIP Accepted Not yet completed |
KIP-949: Add flag to enable the usage of topic separator in MM2 DefaultReplicationPolicy | KAFKA-15102 - Getting issue details... STATUS | mirrormaker | KIP Accepted Not yet completed for 3.6.0. |