You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Release Dates

  • KIP Freeze: January 23, 2018 (a KIP must be accepted by this date in order to be considered for this release)
  • Feature Freeze: January 30, 2018 (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: February 13, 2018 (first RC created now)
  • Release: February 27, 2018 (Tentatively)


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 Damian Guy.

Release Features

This is a list of key features/improvements/bugfixes that we can include with release notes (WIP):

  • TBD
  • Kafka Streams API improvements (KIP-205 / 210 / 220 / 224 / 239)

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

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 this release page for more details of the included tickets.

 

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.

KIPJIRAComponentCommitter
KIP-203: Add toLowerCase support to sasl.kerberos.principal.to.local rule  Unable to render Jira issues macro, execution error. SecurityJason Gustafson
KIP-204 : Adding records deletion operation to the new Admin Client API Unable to render Jira issues macro, execution error. Admin Clientguozhang Wang
KIP-205: Add all() and range() API to ReadOnlyWindowStore Unable to render Jira issues macro, execution error. Streamsguozhang Wang
KIP-210 - Provide for custom error handling when Kafka Streams fails to produce Unable to render Jira issues macro, execution error. StreamsDamian Guy
KIP-215: Add topic regex support for Connect sinks Unable to render Jira issues macro, execution error. ConnectEwen Cheslack-Postava
    

Postponed to subsequent release

 KIPJIRAComponentCommitter
1KIP-48 Delegation token support for Kafka Unable to render Jira issues macro, execution error. Security ?
6KIP-150 - Kafka-Streams Cogroup Unable to render Jira issues macro, execution error. Streamsguozhang Wang

 

 

  • No labels