You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 23
Next »
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.
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 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 |
Unable to render Jira issues macro, execution error.
| core | KIP Accepted InProgress |
| KIP-580: Exponential Backoff for Kafka Clients |
Unable to render Jira issues macro, execution error.
| clients | KIP Accepted Implementation in progress |
| KIP-726: Make the "cooperative-sticky, range" as the default assignor |
Unable to render Jira issues macro, execution error.
| clients | KIP Accepted |
| KIP-770: Replace "buffered.records.per.partition" with "input.buffer.max.bytes" |
Unable to render Jira issues macro, execution error.
| streams | KIP Accepted |
| KIP-793: Allow sink connectors to be used with topic-mutating SMTs |
Unable to render Jira issues macro, execution error.
| connect | Completed |
| KIP-797: Accept duplicate listener on port for IPv4/IPv6 |
Unable to render Jira issues macro, execution error.
| core | KIP Accepted |
| KIP-813: Shareable State Stores |
Unable to render Jira issues macro, execution error.
| streams | KIP Accepted |
| KIP-821: Connect Transforms support for nested structures |
Unable to render Jira issues macro, execution error.
| connect | KIP Accepted |
| KIP-852: Optimize calculation of size for log in remote tier |
Unable to render Jira issues macro, execution error.
| core | KIP Accepted Implementation under review |
| KIP-868 Metadata Transactions |
Unable to render Jira issues macro, execution error.
| core | Accepted Implementation under review |
| KIP-875: First-class offsets support in Kafka Connect |
Unable to render Jira issues macro, execution error.
| connect | Completed In prior releases: connector STOPPED state, offsets read API In this release: Offsets alter and reset APIs |
| KIP-898: Modernize Connect plugin discovery |
Unable to render Jira issues macro, execution error.
| connect | KIP Accepted |
| KIP-902: Upgrade Zookeeper to 3.8.1 |
Unable to render Jira issues macro, execution error.
| core | KIP Accepted Implementation under review |
KIP-917: Additional custom metadata for remote log segment |
Unable to render Jira issues macro, execution error.
| core | KIP Accepted InProgress |
KIP-919: Allow AdminClient to Talk Directly with the KRaft Controller Quorum and add Controller Registration |
Unable to render Jira issues macro, execution error.
| core | KIP Accepted |
KIP-925: Rack aware task assignment in Kafka Streams |
Unable to render Jira issues macro, execution error.
| streams | KIP Accepted Implementation in progress |
| KIP-937: Improve Message Timestamp Validation |
Unable to render Jira issues macro, execution error.
| core | KIP Accepted Implementation in progress |
| KIP-938: Add more metrics for measuring KRaft performance |
Unable to render Jira issues macro, execution error.
| core | KIP Accepted Implementation in progress |
KIP-863: Reduce CompletedFetch#parseRecord() memory copy |
Unable to render Jira issues macro, execution error.
| clients | Completed |
KIP-872: Add Serializer#serializeToByteBuffer() to reduce memory copying |
Unable to render Jira issues macro, execution error.
| clients | KIP Accepted |
KIP-930: Rename ambiguous Tiered Storage Metrics |
Unable to render Jira issues macro, execution error.
| core | KIP Accepted Implementation Draft Ready |
KIP-959: Add BooleanConverter to Kafka Connect |
Unable to render Jira issues macro, execution error.
| connect | Vote in Progress Implementation under review |
Postponed to subsequent release