Management Organization Release tracking Release Cadence Backporting process Backport Criteria Backporting Guide for the Backporter Backporting Guide for Others Generic Release Process GitHub template committers Weekly duties Pull request review process for Janitors team Triage issues for Triage team Backporting PR for Backport team Developer’s Certificate of Origin Development Setup Verifying Your Development backported to these stable releases backport/X.Y This is backport PR, may only be set as part of Backporting process upgrade-impact The code changes have a potential upgrade impact area/* (Optional) Code

Management Organization Release tracking Release Cadence Backporting process Backport Criteria Backporting Guide for the Backporter Backporting Guide for Others Generic Release Process GitHub template committers Weekly duties Pull request review process for Janitors team Triage issues for Triage team Backporting PR for Backport team Developer’s Certificate of Origin Development Setup Verifying Your Development backported to these stable releases backport/X.Y This is backport PR, may only be set as part of Backporting process upgrade-impact The code changes have a potential upgrade impact area/* (Optional) Code

Management Organization Release tracking Release Cadence Backporting process Backport Criteria Backporting guide for the backporter Backporting guide for others Generic Release Process GitHub template committers Weekly duties Pull request review process for Janitors team Triage issues for Triage team Backporting PR for Backport team Developer’s Certificate of Origin Cilium Committer Grant/Revocation Policy backported to these stable releases backport/X.Y This is backport PR, may only be set as part of Backporting process upgrade-impact The code changes have a potential upgrade impact area/* (Optional) Code

Management Organization Release tracking Release Cadence Backporting process Backport Criteria Backporting guide for the backporter Backporting guide for others Generic Release Process GitHub template committers Weekly duties Pull request review process for Janitors team Triage issues for Triage team Backporting PR for Backport team Developer’s Certificate of Origin Cilium Committer Grant/Revocation Policy backported to these stable releases backport/X.Y This is backport PR, may only be set as part of Backporting process upgrade-impact The code changes have a potential upgrade impact area/* (Optional) Code

Release Process GitHub template process Reference steps for the template Minor Release Process Backporting process CI / Jenkins Jobs Overview Triggering Pull-Request Builds With Jenkins Using Jenkins progress, signals reviewers to hold. backport/X.Y This is backport PR, may only be set as part of Backporting process Labels When to set upgrade-impact The code changes have a potential upgrade impact Getting for the template 1. Ensure that the necessary backports have been completed and merged. See Backporting process. 1. Update GitHub project and create vX.Y.Z+1 project if applicable. 2. Update PRs / issues

image Release Management Organization Release tracking Release Cadence Backporting process Backport Criteria Backporting guide Generic Release Process Release Candidate Process Feature Release Process progress, signals reviewers to hold. backport/X.Y This is backport PR, may only be set as part of Backporting process upgrade-impact The code changes have a potential upgrade impact Getting a pull request developers responsible for backporting fixes or preparing upcoming stable releases. Organization Release tracking Release Cadence Backporting process Backport Criteria Backporting guide Generic Release

Follow the Generic Release Process to create the final replace and replace X.Y.0-rcX with X.Y.0 . Backporting process Cilium PRs that are marked with the label needs-backport/X.Y need to be backported to need backpor�ng, from the newest to oldest: $ GITHUB_TOKEN=xxx contrib/backporting/check-stable 1.0 Note contrib/backporting/check-stable accepts a second argument to specify a path to write a nicely-forma�ed one cherry pick fails or every commit is cherry-picked. $ contrib/backporting/cherry-pick ... $ contrib/backporting/cherry-pick Push your backports branch to cilium

to earlier branches. If the content is a new feature designated for the next release, obviously backporting is not appropriate. But if it is a fix or update to an existing topic, don’t forget to cherry-pick

see LICENSE.python for details. The following changes were made to the original sources during backporting: Added self to super calls. Removed from None when raising exceptions. class celery.utils.dispatch

see LICENSE.python for details. The following changes were made to the original sources during backporting: Added self to super calls. Removed from None when raising exceptions. class celery.utils.dispatch