Skip to content

Commit bff0e68

Browse files
committed
Change wording around end of year holidays
Signed-off-by: Jeremy <[email protected]>
1 parent cd25f73 commit bff0e68

File tree

1 file changed

+2
-2
lines changed
  • content/en/blog/_posts/2021-07-20-Kubernetes-Release-Cadence

1 file changed

+2
-2
lines changed

content/en/blog/_posts/2021-07-20-Kubernetes-Release-Cadence/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,8 +16,8 @@ This blog post provides a high level overview about what this means for the Kube
1616
Starting with the [Kubernetes 1.22 release](https://github.com/kubernetes/sig-release/tree/master/releases/release-1.22), a lightweight policy will drive the creation of each release schedule. This policy states:
1717

1818
* The first Kubernetes release of a calendar year should start at the second or third
19-
week of January to provide people more room after coming back from the
20-
winter holidays.
19+
week of January to provide people more time for contributors coming back from the
20+
end of year holidays.
2121
* The last Kubernetes release of a calendar year should be finished by the middle of
2222
December.
2323
* A Kubernetes release cycle has a length of approximately 15 weeks.

0 commit comments

Comments
 (0)