diff options
| author | Antonio Ojea <aojea@redhat.com> | 2021-09-19 15:33:35 +0200 |
|---|---|---|
| committer | Antonio Ojea <aojea@redhat.com> | 2021-09-20 15:13:30 +0200 |
| commit | c2bef44264eb92b938ac00d95b2bade73a698274 (patch) | |
| tree | 97592aef2c97b703324f091a91f5fc6e914481d2 /contributors | |
| parent | 208f7e1aed174d7f507759d390685da84c720738 (diff) | |
cherry-pick policy for alpha and beta features
Diffstat (limited to 'contributors')
| -rw-r--r-- | contributors/devel/sig-release/cherry-picks.md | 6 |
1 files changed, 2 insertions, 4 deletions
diff --git a/contributors/devel/sig-release/cherry-picks.md b/contributors/devel/sig-release/cherry-picks.md index 012a95ae..bf843a3b 100644 --- a/contributors/devel/sig-release/cherry-picks.md +++ b/contributors/devel/sig-release/cherry-picks.md @@ -42,10 +42,8 @@ Again, the emphasis is on critical bug fixes, e.g., - Panic, crash, hang - Security -As a counter example, we would not support backporting a bug fix to an alpha -feature in general. One condition where we would consider is if that bug caused -an issue for in another part of the system even when the alpha feature was -switched off / not in use. +A bugfix for a functional issue (not a data loss or security issue) that only +affects an alpha feature does not qualify as a critical bug fix. If you are proposing a cherry pick and it is not a clear and obvious critical bug fix, please reconsider. If upon reflection you wish to continue, bolster |