Versions Compared

Old Version 16

changes.mady.by.user Divij Vaidya

Saved on

compared with

New Version Current

changes.mady.by.user Divij Vaidya

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This is the release plan for bug fix version 3.5.1. The primary reason for a relatively early patch release for 3.5.x series is to provide a fix for CVE 2023-34455

Release Manager: Divij Vaidya 

Major and minor version releases are driven by the Time Based Release Plan. As a bug fix version, this release will be performed on-demand as sufficient bug fixes aggregate. This page mostly serves to help understand approximate expected release dates, coordinate testing, and track completed and outstanding JIRAs targeted for the release.

Release Date

July 2023

This date is approximate at best and subject to change. Bug fix releases are driven both by the impact of bug fixes that have already been committed and known outstanding issues. Please email the dev list if you think the timeline needs to be adjusted.

Current tentative timelines for the release is as follows (all times in UTC):

  •  3rd July: Publish release plan and share with the community.
  •  3rd - 9th July: Wait for community to backport fixes.
  •  10th 11th 12th July: Prepare the first release candidate and call for vote.
  •  TBD based on vote: Release complete. (Current estimated release date - 18th July).

How to Contribute

  • Open blocker JIRAs on critical issues found. Open non-blocker JIRAs on any other issues found.
  • Participate in fixing, reviewing, and testing important bug fixes. For bug fix releases, testing is among the most valuable contributions, especially for bugs not easily reproduced in unit, integration, or system tests.
  • Vote in RC VOTE threads for the release.

Open Blocker Issues

These are open issues that either:

  • Were marked as blocker because the impact is uncertain and warrants further investigation while blocking release of existing fixes
  • Have been evaluated as important enough that despite existing fixes, the bug fix release should be held until this fix is made due to its criticality.

You can help move us to release faster by contributing fixes or testing of fixes for these issues.

Jira
serverASF JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,customfield_12311032,customfield_12311037,customfield_12311022,customfield_12311027,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,Priority,Priority,Priority,Priority,priority,status,resolution
maximumIssues20
jqlQueryproject = KAFKA AND priority = Blocker AND resolution = Unresolved AND fixVersion = 3.5.1 ORDER BY priority DESC, status DESC, updated DESC
serverId5aa69414-a9e9-3523-82ec-879b028fb15b

Open Critical Issues

These do not need to block the release (or they would be blockers), but they have been evaluated at a high level of significance.

Jira
serverASF JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject = KAFKA AND priority = Critical AND resolution = Unresolved AND fixVersion = 3.5.1 ORDER BY priority DESC, status DESC, updated DESC
serverId5aa69414-a9e9-3523-82ec-879b028fb15b

Open Non-Blocker Issues

These are open issues that developers or users have expressed interest in having in the bugfix release, but should not block a release.

You can help the release process by evaluating any issues here that have not been reviewed and helping determine if it should be in a bug fix release, if this is the appropriate release, and if its priority should be adjusted.

Jira
serverASF JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject = KAFKA AND priority != Blocker AND priority != Critical AND resolution = Unresolved AND fixVersion = 3.5.1 ORDER BY priority DESC, status DESC, updated DESC
serverId5aa69414-a9e9-3523-82ec-879b028fb15b


Merged Issues

These issues have already been resolved and will be included in the release. Each item would appear as is in the release notes.

Jira
serverASF JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject = KAFKA AND fixVersion = 3.5.1 AND resolution != Unresolved ORDER BY priority DESC, status DESC, updated DESC
serverId5aa69414-a9e9-3523-82ec-879b028fb15b