Add graduation criteria and update alpha milestone

Author: bobbypage

keps/sig-node/2000-graceful-node-shutdown/README.md

@@ -530,15 +530,16 @@ Below are some examples to consider, in addition to the aforementioned [maturity
 
 #### Alpha -> Beta Graduation
 
-*   Addresses feedback from alpha testers
-*   Sufficient E2E and unit testing
+- Gather feedback from developers and surveys
+- Complete features A, B, C
+- Tests are in Testgrid and linked in KEP
 
 #### Beta -> GA Graduation
 
-*   Addresses feedback from beta
-*   Sufficient number of users using the feature
-*   Confident that no further API / kubeletConfig configuration options changes are needed
-*   Close on any remaining open issues / bugs
+- N examples of real-world usage
+- N installs
+- More rigorous forms of testing—e.g., downgrade tests and scalability tests
+- Allowing time for feedback
 
 **Note:** Generally we also wait at least two releases between beta and
 GA/stable, because there's no opportunity for user feedback, or even bug reports,
@@ -557,6 +558,16 @@ in back-to-back releases.
 [conformance tests]: https://git.k8s.io/community/contributors/devel/sig-architecture/conformance-tests.md
 -->
 
+#### Alpha -> Beta Graduation
+* Addresses feedback from alpha testers
+* Sufficient E2E and unit testing
+
+#### Beta -> GA Graduation
+* Addresses feedback from beta
+* Sufficient number of users using the feature
+* Confident that no further API / kubelet config configuration options changes are needed
+* Close on any remaining open issues & bugs
+
 ### Upgrade / Downgrade Strategy
 
 <!--

keps/sig-node/2000-graceful-node-shutdown/kep.yaml

@@ -17,7 +17,7 @@ latest-milestone: "v1.20"
 
 # The milestone at which this feature was, or is targeted to be, at each stage.
 milestone:
-  alpha: "v1.21"
+  alpha: "v1.20"
   beta: "x.y"
   stable: "x.y"