Retarget for Kubernetes 1.27

keps/sig-release/3344-release-team-roster/README.md

@@ -255,7 +255,7 @@ The list of roster members will be maintained in a YAML file in https://github.c
 People on the roster can be in one of three roles: Shadow, Member, or Emeritus.
 
 At the time of creation, all former role leads or release leads from any release will be added as emeritus members, or a member if they want.
-The 1.25 EA will lead discussions around which shadows from 1.25 should be placed at the member or shadow level on the release team roster.
+The 1.26 Emeritus Advisor (EA) will lead discussions around which shadows from 1.26 should be placed at the member or shadow level on the release team roster.
 
 Roster Shadows may leave at any time by opening a PR to remove themselves.
 Shadows that do not join a release team for two consecutive releases will generally be removed (although this is at the discretion of SIG Release).
@@ -274,7 +274,7 @@ Anyone may sign up to become a shadow in the future at any time.
 
 ### Release Team Selection
 
-Starting with the Kubernetes 1.26 release team:
+Starting with the Kubernetes 1.27 release team:
 
 Each release team area, with the exception of the lead, will build their teams from a combination of members and shadows from the roster.
 The expected distribution for each area is one lead (who will themselves be a roster member), two roster members, and two roster shadows.
@@ -852,7 +852,7 @@ Major milestones might include:
 - the version of Kubernetes where the KEP graduated to general availability
 - when the KEP was retired or superseded
 -->
-- Kubernetes 1.26: GA and first use
+- Kubernetes 1.27: Stable and first use
 
 ## Drawbacks
 

keps/sig-release/3344-release-team-roster/kep.yaml

@@ -22,16 +22,17 @@ see-also: []
 replaces: []
 
 # The target maturity stage in the current dev cycle for this KEP.
-stage: alpha
+# This is a direct-to-stable process change.
+stage: stable
 
 # 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.26"
+latest-milestone: "v1.27"
 
 # The milestone at which this feature was, or is targeted to be, at each stage.
 milestone:
-  stable: "v1.26"
+  stable: "v1.27"
 
 # The following PRR answers are required at alpha release
 # List the feature gate name and the components for which it must be enabled
@@ -40,3 +41,4 @@ disable-supported: true
 
 # The following PRR answers are required at beta release
 metrics: []
+