Bump release details for mutating admission policy

Author: jpbetz

keps/sig-api-machinery/3962-mutating-admission-policies/README.md

@@ -1097,6 +1097,14 @@ enhancement:
   cluster required to make on upgrade, in order to make use of the enhancement?
 -->
 
+No changes are required for a cluster to make an upgrade and maintain existing behavior.
+There is new API that does not effect the cluster during upgrade. It only has effects
+if it is used after the upgrade.
+
+If a cluster is downgraded, no changes are required. The cluster continues to work as expected since
+the alpha version will have functionality compatible with beta and stable release, any downgrade
+will be to a version that also contains the feature.
+
 ### Version Skew Strategy
 
 <!--
@@ -1112,6 +1120,12 @@ enhancement:
   CRI or CNI may require updating that component before the kubelet.
 -->
 
+This feature is implemented in the kube-apiserver component, skew with other
+kubernetes components do not require coordinated behavior.
+
+Clients should ensure the kube-apiserver is fully rolled out before using the
+feature.
+
 ## Production Readiness Review Questionnaire
 
 <!--

keps/sig-api-machinery/3962-mutating-admission-policies/kep.yaml

@@ -28,11 +28,11 @@ stage: alpha
 # The most recent milestone for which work toward delivery of this KEP has been
 # done. This can be the current (upcoming) milestone, if it is being actively
 # worked on.
-latest-milestone: "v1.30"
+latest-milestone: "v1.32"
 
 # The milestone at which this feature was, or is targeted to be, at each stage.
 milestone:
-  alpha: "v1.30"
+  alpha: "v1.32"
 
 # The following PRR answers are required at alpha release
 # List the feature gate name and the components for which it must be enabled