kep 3203 add test plan graduation criteria

keps/sig-security/3203-auto-refreshing-official-cve-feed/README.md

@@ -323,68 +323,13 @@ when drafting this test plan.
 [testing-guidelines]: https://git.k8s.io/community/contributors/devel/sig-testing/testing.md
 -->
 
-[ ] I/we understand the owners of the involved components may require updates to
-existing tests to make this code solid enough prior to committing the changes necessary
-to implement this enhancement.
+This is a process KEP implemented using periodic prow job. This KEP is not implemented for any functional use cases of kubernetes. So no e2e/unit/integration tests are applicable and going forward test plan will mostly include the scenarios around monitoring of the prow job for any failures as and when needed. 
 
-##### Prerequisite testing updates
-
-<!--
-Based on reviewers feedback describe what additional tests need to be added prior
-implementing this enhancement to ensure the enhancements have also solid foundations.
--->
-
-##### Unit tests
-
-<!--
-In principle every added code should have complete unit test coverage, so providing
-the exact set of tests will not bring additional value.
-However, if complete unit test coverage is not possible, explain the reason of it
-together with explanation why this is acceptable.
--->
-
-<!--
-Additionally, for Alpha try to enumerate the core package you will be touching
-to implement this enhancement and provide the current unit coverage for those
-in the form of:
-- <package>: <date> - <current test coverage>
-The data can be easily read from:
-https://testgrid.k8s.io/sig-testing-canaries#ci-kubernetes-coverage-unit
-
-This can inform certain test coverage improvements that we want to do before
-extending the production code to implement this enhancement.
--->
-
-- `<package>`: `<date>` - `<test coverage>`
-
-##### Integration tests
-
-<!--
-This question should be filled when targeting a release.
-For Alpha, describe what tests will be added to ensure proper quality of the enhancement.
-
-For Beta and GA, add links to added tests together with links to k8s-triage for those tests:
-https://storage.googleapis.com/k8s-triage/index.html
--->
-
-- <test>: <link to test coverage>
-
-##### e2e tests
-
-<!--
-This question should be filled when targeting a release.
-For Alpha, describe what tests will be added to ensure proper quality of the enhancement.
-
-For Beta and GA, add links to added tests together with links to k8s-triage for those tests:
-https://storage.googleapis.com/k8s-triage/index.html
-
-We expect no non-infra related flakes in the last month as a GA graduation criteria.
--->
+### Graduation Criteria
 
-- <test>: <link to test coverage>
--->
+#### Alpha
 
-### Graduation Criteria
+- KEP implementation is still in alpha and will be moved to beta based on community feedback within the next couple of release cycles.
 
 <!--
 **Note:** *Not required until targeted at a release.*

keps/sig-security/3203-auto-refreshing-official-cve-feed/kep.yaml

@@ -27,16 +27,16 @@ see-also:
 #
 stage: alpha
 
-#latest-milestone: "v1.25"
-#
-#milestone:
-#  alpha: "v1.25"
-#  beta: ""
-#  stable: ""
-#
+latest-milestone: "v1.25"
+
+milestone:
+  alpha: "v1.25"
+  beta: "TBD"
+  stable: "TBD"
+
 ## This KEP enhances Kubernetes testing.  It does not directly impact any component.
-#feature-gates: []
-#disable-supported: true
-#metrics: []
+feature-gates: []
+disable-supported: true
+metrics: []