-
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
pkg/kepval: enable PRR check for implemented KEPs #3007
Commits on Oct 13, 2021
-
pkg/kepval: require prr check for implemented keps
Tests will fail at this commit, subsequent commits update data to resolve the failures.
Configuration menu - View commit details
-
Copy full SHA for c48b033 - Browse repository at this point
Copy the full SHA c48b033View commit details -
helper script to edit keps en-masse, hardcoded in this case to make a guess at stage and latest-milestone for keps with status: implemented ./hack/edit-keps.py --keps-dir ./keps
Configuration menu - View commit details
-
Copy full SHA for ed17414 - Browse repository at this point
Copy the full SHA ed17414View commit details -
keps: add latest-milestone and stage to implemented KEPs
Added via hack/edit-keps.py
Configuration menu - View commit details
-
Copy full SHA for 761668f - Browse repository at this point
Copy the full SHA 761668fView commit details -
keps/sig-cli: 2206 status: implementable
Looking through history, consensus seemed to be that implemented status is reserved for KEPs that have `stage: stable`, so this should remain at implementable
Configuration menu - View commit details
-
Copy full SHA for 105f034 - Browse repository at this point
Copy the full SHA 105f034View commit details -
keps/sig-release: 1498 stage: stable
This is implemented so its stage should be stable
Configuration menu - View commit details
-
Copy full SHA for dd3cb63 - Browse repository at this point
Copy the full SHA dd3cb63View commit details -
keps/sig-release: 0000 stage: stable
This is implemented so its stage should be stable
Configuration menu - View commit details
-
Copy full SHA for 6411a4d - Browse repository at this point
Copy the full SHA 6411a4dView commit details -
keps/sig-testing: 2539 status: implementable
It seems consensus is that implemented should only be used once stage is stable. We're not there yet on this KEP, so drop back to implementable
Configuration menu - View commit details
-
Copy full SHA for cf70bb1 - Browse repository at this point
Copy the full SHA cf70bb1View commit details -
keps/prod-readiness: add sig-architecture/1143
This was marked as stable in v1.21 as of 2021-04-xx. The PRR check is only valid for anything v1.21 or later, but wasn't marked as required until 2021-05-05. I'm not sure if this never went through review, was previously exempt, etc.
Configuration menu - View commit details
-
Copy full SHA for a5a7071 - Browse repository at this point
Copy the full SHA a5a7071View commit details -
keps/prod-readiness: add sig-testing/2539
This went to beta in v1.21 before PRR was mandated as required. It's a tooling/process KEP that doesn't affect the contents of a kubernetes release, so I expect this to be a rubber stamp
Configuration menu - View commit details
-
Copy full SHA for 3f4b245 - Browse repository at this point
Copy the full SHA 3f4b245View commit details -
keps/prod-readiness: add sig-cli/2206
This was retroactively marked as implemented @ beta during v1.22. It's not clear to me whether this should have gone through PRR
Configuration menu - View commit details
-
Copy full SHA for a28ce6d - Browse repository at this point
Copy the full SHA a28ce6dView commit details -
Configuration menu - View commit details
-
Copy full SHA for 6f464ad - Browse repository at this point
Copy the full SHA 6f464adView commit details -
Configuration menu - View commit details
-
Copy full SHA for 4b78b37 - Browse repository at this point
Copy the full SHA 4b78b37View commit details