...
- KIP Freeze: 3rdJuly (Wednesday)
- 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: 24th July (Wednesday 8th August (Thursday)
- major features merged & working on stabilisation, minor features have PR, release branch cut; anything not in this state will be automatically moved to the next release in JIRA
- Code Freeze: 7th 29th August (WednesdayThursday)
- At least two weeks of stabilization will follow Code Freeze, meaning we expect to release no earlier than August 14th September 12th. We will move as fast as we can, and aim completion the earliest we can in AugustSeptember.
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 earliest possible release date is 2w after code freeze, release candidates (RCs) will roll out as needed until the release vote passes.
...
Postponed to subsequent release
KIP | JIRA | ComponentStatus | KIP-1025: Optionally URL-encode clientID and clientSecret in authorization header | Jira |
---|
server | ASF JIRA |
---|
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,customfield_12311032,customfield_12311037,customfield_12311022,customfield_12311027,priority,status,resolution |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,Priority,Priority,Priority,Priority,priority,status,resolution |
---|
serverId | 5aa69414-a9e9-3523-82ec-879b028fb15b |
---|
key | KAFKA-16345 |
---|
|
| clients |
KIP approved1023: Follower fetch from tiered offset15433coreKIP approved1007 Introduce Remote Storage Not Ready Exception15876storageKIP approved1005: Expose EarliestLocalOffset and TieredOffset15857Postponed to subsequent release