Skip to content

Commit 381ef6d

Browse files
committed
move KEP process proposal to architecture directory.
...also change filename to match title
1 parent ff8daa4 commit 381ef6d

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

contributors/design-proposals/kep-development-process.md renamed to contributors/design-proposals/architecture/kubernetes-enhancement-proposal-process.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
# Kubernetes Enhancement Proposal (KEP) Process
1+
# Kubernetes Enhancement Proposal Process
22

33
## Metadata
44
```
@@ -34,6 +34,7 @@ metadata:
3434
## Summary
3535

3636
A standardized development process for Kubernetes is proposed in order to:
37+
3738
- provide a common structure for proposing changes to Kubernetes
3839
- ensure that the motivation for a change is clear
3940
- allow for the enumeration stability milestones and stability graduation
@@ -51,6 +52,9 @@ A standardized development process for Kubernetes is proposed in order to:
5152
completion across one or more releases while stakeholders are adequately
5253
represented throughout the process
5354

55+
This process is supported by a unit of work called a Kubernetes Enhancement
56+
Proposal or KEP.
57+
5458
## Motivation
5559

5660
For cross project SIGs such as SIG PM and SIG Release an abstraction beyond a

0 commit comments

Comments
 (0)