Release Dates
- KIP Freeze: Jan 22, 2020 (a KIP must be accepted by this date in order to be considered for this release)
- Feature Freeze: Jan 29, 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: Feb 12, 2020
- Release: Feb 26, 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 David Arthur.
Planned KIPs
- KIP-150 - Kafka-Streams Cogroup
- KIP-280: Enhanced log compaction
- KIP-352: Distinguish URPs caused by reassignment
- KIP-360: Improve handling of unknown producer
- KIP-396: Add Reset/List Offsets Operations to AdminClient
- KIP-444: Augment metrics for Kafka Streams (some parts in 2.4, some TBD)
- KIP-455: Create an Administrative API for Replica Reassignment
- KIP-467: Augment ProduceResponse error messaging for specific culprit records
- KIP-511: Collect and Expose Client's Name and Version in the Brokers (new metrics)
- KIP-515: Enable ZK client to use the new TLS supported authentication
- KIP-523: Add KStream#toTable to the Streams DSL
- KIP-524: Allow users to choose config source when describing configs
- KIP-527: Add VoidSerde to Serdes
- KIP-546: Add quota-specific APIs to the Admin Client, redux
- KIP-555: Deprecate Direct Zookeeper access in Kafka Administrative Tools
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