-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
KEP: Enhance the KEP implementation #617
Comments
/assign @justaugustus @calebamiles @jdumars |
/stage beta |
...because the label exists now: |
Why not go all the way and move them to a database? That's pretty clearly where we're eventually going. And it would solve the autonumbering problem. |
Looking over the points, it looks like much of this is done. (Perhaps checkboxes could be clearer) |
Hey @vbatts! :) We've still got some work to do here before I'd consider the process
That said, you're right, we should get this issue updated! Will handle. |
Right on! |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@kubernetes/enhancements -- spoke w/ Lauri earlier and I think we should:
Sound good? |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
Rotten issues close after 30d of inactivity. Send feedback to sig-contributor-experience at kubernetes/community. |
@k8s-triage-robot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Kubernetes Enhancement Proposal Implementation
/sig architecture
/kind feature
/milestone v1.13
Project tracking board
https://github.com/orgs/kubernetes/projects/5
High-level implementation plan
Define
scope
field for KEP metadata #2311Before a KEP gets filed
needs-triage
should be other SIGs’ responsibility.Organize
- Stricter validation for KEPs — time to ratchet up presubmits -- can do it, but need to ensure it’s nonblocking as a presubmit so people can slowly fix these things. Secondary presubmit report? Flag or boolean option in kepeval tool?
- Acceptance criteria: all KEPs are actually in proper forma
kind/kep
label for [k/community] and [k/features]k/community
:kind/kep
(done via owner file) - no longer relevantorg:kubernetes label:kind/kep
, so we can identify active PRs tok/community
and reroute the PR authors tok/enhancements
(depending on the state)For
k/enhancements
(fkak/features
):kind/kep
kind/kep
, differentiating them fromkind/feature
kind/kep
from [k/community] once KEP migration is completeVisibility and Automation
keps/
(KEPs)design-proposals/
(historical design proposals from https://git.k8s.io/community/contributors/design-proposals)arch[itecture]|design/
(design principles of Kubernetes, derived from reorganizing https://git.k8s.io/community/contributors/devel, mentioned here)Improve KEP Template to drive consistent user experience and minds
Other to-do's for this to become
stable
- [ ] Enable versioning and consistent data validation for KEPs #2348
The text was updated successfully, but these errors were encountered: