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

Compare with Current View Page History

« Previous Version 4 Next »

Release Dates

  • Feature Freeze: TBD (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: TBD (first RC created now)
  • Release: June 2017 

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.

Release Manager

The release manager is Ismael Juma.

Release Features

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

  • TBD

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 system tests. We want to preserve the tradition of high-quality releases in Apache Kafka. 

After code freeze:

  • Test the release candidates
  • Open bugs on important issues found
  • Fix 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 T Created Updated Due Assignee Reporter P Status Resolution
Loading...
Refresh

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.

KIPs Bumped to Next Release

KIPJIRAStatusComponentCommitter
     
  • No labels