@@ -267,10 +267,10 @@ With the proposed change in cadence, the notional schedules for the remainder of
267
267
| 49 | 3 | 14 (December 06) |
268
268
269
269
This KEP will be in the ` alpha ` stage for the Kubernetes 1.22 Release. During
270
- this time, SIG- Release will focus on communication of the cadence change through
270
+ this time, SIG Release will focus on communication of the cadence change through
271
271
all available mechanisms. The KEP will promote to the ` beta ` stage for the
272
272
Kubernetes 1.23 Release, which will be the final release of 2021. After
273
- the 1.23, 1.24, and 1.25 Releases, will will collect feedback and incorporate
273
+ the 1.23, 1.24, and 1.25 Releases, SIG Release will collect feedback and incorporate
274
274
that feedback into the lightweight framework surrounding release schedule
275
275
development and promote this KEP to ` stable ` for the 1.26 Release.
276
276
@@ -369,7 +369,7 @@ Some downstream projects, such as Helm have already begun
369
369
[ planning] ( https://github.com/helm/community/blob/main/hips/hip-0002.md#minor-releases )
370
370
for this change.
371
371
372
- To mitigate this risk, SIG- Release will perform the following actions:
372
+ To mitigate this risk, SIG Release will perform the following actions:
373
373
374
374
* Once this KEP has merged, an email will be sent to the [ k/dev] ( https://groups.google.com/g/kubernetes-dev ) list
375
375
* A community meeting occurring during the 1.22 Release Cycle will be used to communicate the change
0 commit comments