Skip to content

Release 2.2.2 #4415

@shaun-nx

Description

@shaun-nx

Issue to track the release tasks for 2.2.2 following our release process.

Tasks

  • Cherry Pick required PRs to release-2.2 branch
  • Run the Release PR workflow to update the repo files for the release.
  • Update the README to include information about the release.
  • Update the changelog. There is going to be a new blank section generated by the automation that needs to be adjusted accordingly.
    • At the top there will be a list of all PRs that are labeled with release-notes.
      The changelog includes only important (from the user perspective)
      changes to NGF. This is in contrast with the autogenerated full changelog, which is created in the next
      step. As a starting point, copy the important features, bug fixes, and dependencies from the autogenerated
      draft of the full changelog. This draft can be found under
      the GitHub releases after the release branch is
      created. If included, use the Release Notes specified in a PR.
    • If the supported Gateway API minor version has changed since the last release, add a note to the release notes explaining if the previous version is no longer supported.
    • Merge the release PR once it has received all necessary approvals.

Production release

Start a production release by running the CI workflow with the following inputs:

  • Select release branch release-2.2
  • Check is_production_release checkbox
  • Set release_version to the release tag v2.2.2
  • Set operator_version to to v1.0.2
  • Uncheck dry_run

Operator certification

Build and & Certify Operator Bundle

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

Status

✅ Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions