-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Production readiness review process #1194
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
Comments
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. |
/remove-lifecycle stale does this really need an issue in addition to the KEP? It's a process / tooling change not a user-facing change...does that matter? |
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. |
/remove-lifecycle stale |
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. |
/remove-lifecycle stale |
Hiya, is this still needed, especially given #1707? |
We're not closing enhancement issues until they are completed. This one isn't e.g. because PRR is not enforced on each KEP. So it is needed. |
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. |
/remove-lifecycle stale @johnbelamaric - given we're going to enforce PRR for 1.20, I think we need to update some doc maybe? and close this one? |
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. |
/remove-lifecycle stale Some more discussion was requested here - will happen next week. @johnbelamaric |
This has been implemented: https://github.com/kubernetes/enhancements/tree/master/keps/sig-architecture/1194-prod-readiness /close |
@johnbelamaric: 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. |
Enhancement Description
The text was updated successfully, but these errors were encountered: