Versions Compared

Key

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

...

Tag your PR with one or more of the backport labels (like backport-21.1.x, for the 21.1 release) to indicate that it should be backported once merged on master.

“Must check” for reviewers of backport PRs

  • Double check the PR is eligible for backport as per this linked page.

  • Verify that the backport PR does not add a cluster version nor a version gate.
    Ask on #engineering if you need details about why backports must never add cluster versions or version gates.

  • Check the release notes in the commit messages, to ensure they are applicable to the branch (if a release note refers to another change / PR that is not being backported, or that may be backported later, suggest a rephrasing.)

Blathers will automatically backport PRs with backport tags

...