This is the release plan for bug fix version 2.2.1.

Release Manager:  Vahid Hashemian

PMC Release Manager (responsible for final release steps): TBD

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 Dates

  • Release: May 2019

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.

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.

Key Summary T Created Updated Assignee P Status Resolution Component/s

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.

Key Summary T Updated Assignee P Status Resolution Component/s

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.

Key Summary T Updated Assignee P Status Resolution Component/s

  • No labels