From 6f31397167e0f2d61014cc43966311a05f61ff81 Mon Sep 17 00:00:00 2001 From: fabriziopandini Date: Wed, 15 Mar 2023 16:03:09 +0100 Subject: [PATCH] allow backport for experimental features --- CONTRIBUTING.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 4b138a414e29..37f76e1a96ae 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -102,6 +102,15 @@ We generally allow backports of following changes only to the latest supported b - Improvements to CI signal - Improvements to the test framework +While we recommend to target following type of changes to the next minor release, CAPI maintainers will also consider +exceptions for backport of following changes only to the latest supported branch: +- Enhancements or additions to experimental Cluster API features, with the goal of allowing faster adoption and iteration; + Please note that stability of the branch will always be top priority while evaluating those PRs, and thus approval + requires /lgtm from at least two maintainers that, on top of checking that the backport is not introducing any breaking + change for either API or behavior, will evaluate if the impact of those backport is limited and well-scoped e.g. + by checking that those changes should not touch non-experimental code paths like utils and/or by applying other + considerations depending on the specific PR. + Like any other activity in the project, backporting a fix/change is a community-driven effort and requires that someone volunteers to own the task. In most cases, the cherry-pick bot can (and should) be used to automate opening a cherry-pick PR.