diff options
| author | Kubernetes Submit Queue <k8s-merge-robot@users.noreply.github.com> | 2017-09-26 13:03:00 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-09-26 13:03:00 -0700 |
| commit | 1eb3c68dab87330aa3352aba81ef4780fefef508 (patch) | |
| tree | 07d0ce4ddac498e8fcf3666efd57a70c6cca1fcb /generator | |
| parent | 5d96914f550f17faff599367e488b8c010ca0e22 (diff) | |
| parent | fcc75ae13bfb6dc7ac79f16fc6170a89a88cb40d (diff) | |
Merge pull request #1133 from jbeda/kep-focus
Automatic merge from submit-queue. .
Clarify relationship of KEP to release note process
I'm opening this up to have a discussion on what the relationship between a KEP and the release note process is. I see KEPs being most useful for things that will often span releases. I *want* us to think bigger and across multiple releases. Often times a KEP will be discussed and accepted before and outside of the release cycle.
I've also moved some stuff around so that this doc stands more on its own vs. being a "delta" on our current process. In a years time this will be our current process and this won't read as clearly.
Diffstat (limited to 'generator')
0 files changed, 0 insertions, 0 deletions