From 8bb5f4b85888734076bfe7944b42a605df0b57ec Mon Sep 17 00:00:00 2001 From: fabriziopandini Date: Thu, 8 Sep 2022 10:01:45 +0200 Subject: [PATCH] clarify-backport-policy --- CONTRIBUTING.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 59afa82623fc..4479b1e49d4a 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -78,7 +78,14 @@ The test module, clusterctl, and experiments do not provide any backward compati #### Backporting a patch We only accept backports of critical bugs, security issues, or bugs without easy workarounds, any -backport MUST not be breaking for either API or behavioral changes. +backport MUST not be breaking for either API or behavioral changes. In order to improve user/developer experience +maintainers can choose to backport: +- Doc improvements +- Improvements to CI signal +- Improvements to the test framework (enabling improvements to provider's test signal) +- Cert-manager bump (to avoid having branch using cert-manager versions out of support, when possible) +- Changes required to support new Kubernetes versions, when possible. + We generally do not accept PRs against older release branches. ### APIs