cherry-pick policy for alpha and beta features
This commit is contained in:
parent
208f7e1aed
commit
c2bef44264
|
|
@ -42,10 +42,8 @@ Again, the emphasis is on critical bug fixes, e.g.,
|
||||||
- Panic, crash, hang
|
- Panic, crash, hang
|
||||||
- Security
|
- Security
|
||||||
|
|
||||||
As a counter example, we would not support backporting a bug fix to an alpha
|
A bugfix for a functional issue (not a data loss or security issue) that only
|
||||||
feature in general. One condition where we would consider is if that bug caused
|
affects an alpha feature does not qualify as a critical bug fix.
|
||||||
an issue for in another part of the system even when the alpha feature was
|
|
||||||
switched off / not in use.
|
|
||||||
|
|
||||||
If you are proposing a cherry pick and it is not a clear and obvious critical
|
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
|
bug fix, please reconsider. If upon reflection you wish to continue, bolster
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue