diff options
| author | Tim Pepper <tpepper@vmware.com> | 2019-09-11 14:26:37 -0700 |
|---|---|---|
| committer | Tim Pepper <tpepper@vmware.com> | 2019-09-20 08:31:00 -0700 |
| commit | 4cde9de6e49824e236c3912655eae48eecc0a1b9 (patch) | |
| tree | 378b3e2902c9a831ebe0e325ac841422082b17cf /vendor/github.com/client9/misspell/scripts/pre-commit.sh | |
| parent | cd9cfba337a111e71060f9eaa0e7bbcf043a9427 (diff) | |
devel guide: add words on cherry pick review process
There has been a fair amount of ambiguity, even deliberately, around
what is a valid candidate for backporting to a stable release branch of
Kubernetes. For some the criteria is simply "critical bug fixes", but
this is also something that lacks definition. This documentation update
attempts to better describe what is expected of and what can be expected
by somebody proposing a cherry-pick on one of our stable release branches.
Signed-off-by: Tim Pepper <tpepper@vmware.com>
Diffstat (limited to 'vendor/github.com/client9/misspell/scripts/pre-commit.sh')
0 files changed, 0 insertions, 0 deletions