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 TBD
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 | JIRA | Component |
|---|
KIP-150 - Kafka-Streams Cogroup |
Unable to render Jira issues macro, execution error.
| Streams |
KIP-352: Distinguish URPs caused by reassignment |
Unable to render Jira issues macro, execution error.
Unable to render Jira issues macro, execution error.
Unable to render Jira issues macro, execution error.
| Core |
KIP-360: Improve reliability of idempotent/transactional producer |
Unable to render Jira issues macro, execution error.
| Core/Clients |
| KIP-396: Add Reset/List Offsets Operations to AdminClient |
Unable to render Jira issues macro, execution error.
| Clients |
| KIP-447: Producer scalability for exactly once semantics (partial) |
Unable to render Jira issues macro, execution error.
| Streams |
| KIP-455: Create an Administrative API for Replica Reassignment |
Unable to render Jira issues macro, execution error.
| Core |
| KIP-511: Collect and Expose Client's Name and Version in the Brokers (new metrics) |
Unable to render Jira issues macro, execution error.
| Core/Clients |
| KIP-515: Enable ZK client to use the new TLS supported authentication |
Unable to render Jira issues macro, execution error.
| Core |
| KIP-523: Add KStream#toTable to the Streams DSL |
Unable to render Jira issues macro, execution error.
| Streams |
| KIP-524: Allow users to choose config source when describing configs |
Unable to render Jira issues macro, execution error.
| Core |
| KIP-526: Reduce Producer Metadata Lookups for Large Number of Topics |
Unable to render Jira issues macro, execution error.
| Clients |
| KIP-527: Add VoidSerde to Serdes |
Unable to render Jira issues macro, execution error.
| Streams |
| KIP-530: Consider renaming 'UsePreviousTimeOnInvalidTimeStamp' class to 'UsePartitionTimeOnInvalidTimeStamp' |
Unable to render Jira issues macro, execution error.
| Streams |
| KIP-531: Drop support for Scala 2.11 in Kafka 2.5 |
Unable to render Jira issues macro, execution error.
| Core |
| KIP-535: Allow state stores to serve stale reads during rebalance |
Unable to render Jira issues macro, execution error.
| Streams |
| KIP-537: Increase default zookeeper session timeout |
Unable to render Jira issues macro, execution error.
| Core |
| KIP-538: Add a metric tracking the number of open connections with a given SSL cipher type |
Unable to render Jira issues macro, execution error.
| Core |
| KIP-541: Create a fetch.max.bytes configuration for the broker |
Unable to render Jira issues macro, execution error.
| Core |
| KIP-543: Expand ConfigCommand's non-ZK functionality |
Unable to render Jira issues macro, execution error.
| Core |
| KIP-553: Disable all SSL protocols except TLSV1.2 by default. |
Unable to render Jira issues macro, execution error.
| Core |
| KIP-555: Deprecate Direct Zookeeper access in Kafka Administrative Tools (partial in 2.5) |
Unable to render Jira issues macro, execution error.
| Core |
| KIP-558: Track the set of actively used topics by connectors in Kafka Connect |
Unable to render Jira issues macro, execution error.
| Connect |
| KIP-559: Make the Kafka Protocol Friendlier with L7 Proxies |
Unable to render Jira issues macro, execution error.
| Core |
| KIP-562: Allow fetching a key from a single partition rather than iterating over all the stores on an instance |
Unable to render Jira issues macro, execution error.
| Streams |
Postponed KIPs
| KIP | JIRA | Component |
|---|
| KIP-158: Kafka Connect should allow source connectors to set topic-specific settings for new topics |
Unable to render Jira issues macro, execution error.
| Connect |
| KIP-216: IQ should throw different exceptions for different errors |
Unable to render Jira issues macro, execution error.
| Streams |
KIP-280: Enhanced log compaction |
Unable to render Jira issues macro, execution error.
| Core |
| KIP-399: Extend ProductionExceptionHandler to cover serialization exceptions |
Unable to render Jira issues macro, execution error.
| Streams |
| KIP-401: TransformerSupplier/ProcessorSupplier StateStore connecting |
Unable to render Jira issues macro, execution error.
| Streams |
| KIP-444: Augment metrics for Kafka Streams (some parts in 2.4, some TBD) |
Unable to render Jira issues macro, execution error.
| Streams |
| KIP-467: Augment ProduceResponse error messaging for specific culprit records |
Unable to render Jira issues macro, execution error.
| Core/Clients |
| KIP-514: Add a bounded flush() API to Kafka Producer |
Unable to render Jira issues macro, execution error.
| Clients |
| KIP-544: Make metrics exposed via JMX configurable |
Unable to render Jira issues macro, execution error.
| Core |
| KIP-551: Expose disk read and write metrics |
Unable to render Jira issues macro, execution error.
| Core |
|
|
|
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
| key |
priority |
summary |
type |
assignee |
status |
created |
updated |
reporter |
resolution |
JQL and issue key arguments for this macro require at least one Jira application link to be configured
|