summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorcaleb miles <caselim@gmail.com>2017-09-26 01:29:57 -0700
committercaleb miles <caselim@gmail.com>2017-09-26 01:42:36 -0700
commitddeb2b4b547109d3e757cc0ee27ccb4acfd25959 (patch)
treee269ee81574b07f81ee3b741254e67b134089911
parent71344d2917dff540437e93b77689453cdba13b0c (diff)
move KEP process proposal to architecture directory.
...also change filename to match title
-rw-r--r--contributors/design-proposals/architecture/kubernetes-enhancement-proposal-process.md (renamed from contributors/design-proposals/kep-development-process.md)6
1 files changed, 5 insertions, 1 deletions
diff --git a/contributors/design-proposals/kep-development-process.md b/contributors/design-proposals/architecture/kubernetes-enhancement-proposal-process.md
index 03f5a336..c0b97d07 100644
--- a/contributors/design-proposals/kep-development-process.md
+++ b/contributors/design-proposals/architecture/kubernetes-enhancement-proposal-process.md
@@ -1,4 +1,4 @@
-# Kubernetes Enhancement Proposal (KEP) Process
+# Kubernetes Enhancement Proposal Process
## Metadata
```
@@ -34,6 +34,7 @@ metadata:
## Summary
A standardized development process for Kubernetes is proposed in order to:
+
- provide a common structure for proposing changes to Kubernetes
- ensure that the motivation for a change is clear
- allow for the enumeration stability milestones and stability graduation
@@ -51,6 +52,9 @@ A standardized development process for Kubernetes is proposed in order to:
completion across one or more releases while stakeholders are adequately
represented throughout the process
+This process is supported by a unit of work called a Kubernetes Enhancement
+Proposal or KEP.
+
## Motivation
For cross project SIGs such as SIG PM and SIG Release an abstraction beyond a