KIP Freeze: (A KIP must be accepted by this date in order to be considered for this release. Note, any KIP that may not be implemented in a week, or that might destabilize the release, should be deferred.)
Feature Freeze(new date): 28 (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(new date): 11 :
At least two weeks of stabilization will follow Code Freeze.
project = KAFKA AND fixVersion = 3.01.0 AND status not in (resolved, closed) ORDER BY priority DESC, status DESC, updated DESC
serverId
5aa69414-a9e9-3523-82ec-879b028fb15b
...
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.