THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Release Dates
- KIP Freeze: May 20, 2020 (a KIP must be accepted by this date in order to be considered for this release)
- Feature Freeze: May 27, 2020 (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: June 10, 2020
- Release: June 24, 2020
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 target release date is fixed at ~2w after code freeze, RCs will roll out as needed until the release vote passes.
The release manager is Randall Hauch.
Planned KIPs
Postponed KIPs
| KIP | JIRA | Component |
|---|---|---|
| KIP-81: Bound Fetch memory usage in the consumer |
| Clients |
| KIP-280: Enhanced log compaction |
| Core |
| KIP-359: Verify leader epoch in produce requests |
| Core |
| KIP-441: Smooth Scaling Out for Kafka Streams (remainder) |
| Streams |
| KIP-444: Augment metrics for Kafka Streams (remainder) |
| Streams |
| KIP-466: Add support for List<T> serialization and deserialization |
| Streams/Clients |
| KIP-497: Add inter-broker API to alter ISR |
| Core |
| KIP-557: Add emit on change support for Kafka Streams (remainder) |
| Streams |
| KIP-580: Exponential Backoff for Kafka Clients |
| Core/Clients |
| KIP-584: Versioning scheme for features |
| Core/Clients |
| KIP-588: Allow producers to recover gracefully from transaction timeouts |
| Core/Clients |
| KIP-608 - Expose Kafka Metrics in Authorizer |
| Core |
| KIP-611: Improved Handling of Abandoned Connectors and Tasks |
| Connect |
| KIP-612: Ability to Limit Connection Creation Rate on Brokers |
| Core |
| KIP-613: Add end-to-end latency metrics to Streams (remainder) |
| Streams |
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 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 RCs. Even though only PMC votes are binding, community votes are super important as we evaluate the readiness of the release