You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 16
Next »
Release Dates
(all are in 2023)
- KIP Freeze: 22nd November (Wednesday)
- 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: 6th December (Wednesday)
- 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: 20th December (Wednesday)
- At least two weeks of stabilization will follow Code Freeze, meaning we expect to release no earlier than January 3rd. We will move as fast as we can, and aim completion the earliest we can in January.
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 Stanislav Kozlovski
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.7.0 release page for more details of the included tickets (requires logging in to the Apache Kafka Jira project).
Planned KIP Content
Note: The planned content is not binding - the final content will be based on the features committed by the branch-cutting date.
See Kafka Improvement Proposals for the full list of KIPs.
If you do not see your KIP here and want to, please reply to the mailing list thread about the release!
| KIP | JIRA | Component | Status |
|---|
| KIP-960: Single-key single-timestamp IQv2 for state stores |
Unable to render Jira issues macro, execution error.
| streams | |
| KIP-405: Kafka Tiered Storage |
Unable to render Jira issues macro, execution error.
Unable to render Jira issues macro, execution error.
| core | A major part went out with 3.6.0. A minor part of the KIP is to be completed in 3.7.0. |
| KIP-890: Transactions Server-Side Defense |
Unable to render Jira issues macro, execution error.
| core | Part 1 Completed |
KIP-925: Rack aware task assignment in Kafka Streams |
Unable to render Jira issues macro, execution error.
| streams | Partially implemented in 3.6 Targetting completion 3.7 |
| KIP-938: Add more metrics for measuring KRaft performance |
Unable to render Jira issues macro, execution error.
Unable to render Jira issues macro, execution error.
| core | Majority was completed in 3.6. The remaining minority will be done now in 3.7.0 |
| KIP-580: Exponential Backoff for Kafka Clients |
Unable to render Jira issues macro, execution error.
| clients | Implemented Plan to release it in 3.7.0 |
| KIP-770: Replace "buffered.records.per.partition" & "cache.max.bytes.buffering" with "{statestore.cache}/{input.buffer}.max.bytes" |
Unable to render Jira issues macro, execution error.
| streams | Partly implemented, PRs open for the rest but needs reviews |
| KIP-858: Handle JBOD broker disk failure in KRaft |
Unable to render Jira issues macro, execution error.
| core | KIP Accepted Implementation not yet completed |
| KIP-980: Allow creating connectors in a stopped state |
Unable to render Jira issues macro, execution error.
| connect | KIP Accepted Implementation under review |
| KIP-963: Add more metrics to Tiered Storage |
Unable to render Jira issues macro, execution error.
| core | Under discussion. Targetting 3.7 |
| KIP-976: Cluster-wide dynamic log adjustment for Kafka Connect |
Unable to render Jira issues macro, execution error.
| connect | KIP Accepted PR out |
| KIP-848: The Next Generation of the Consumer Rebalance Protocol |
Unable to render Jira issues macro, execution error.
| core | KIP Accepted Targetting a Preview in 3.7 |
| KIP-985: Add reverseRange and reverseAll query over kv-store in IQv2 |
Unable to render Jira issues macro, execution error.
| streams | KIP Accepted
PR Merged Need update Javadoc |
| KIP-988: Streams Standby Update Listener |
Unable to render Jira issues macro, execution error.
| streams | KIP Accepted |
| KIP-992: Proposal to introduce IQv2 Query Types: TimestampedKeyQuery and TimestampedRangeQuery |
Unable to render Jira issues macro, execution error.
| streams | KIP Accepted
PR Under review |
| KIP-975: Docker Image for Apache Kafka |
Unable to render Jira issues macro, execution error.
|
| KIP Accepted PR Under review |
Postponed to subsequent release