Add Kubernetes 1.24 release outline

[JamesLaverack]

What type of PR is this:

/kind documentation

What this PR does / why we need it:

Add the initial outline for the Kubernetes 1.24 release cycle, based on the outline from the release cadence blog post.

Which issue(s) this PR fixes:

Special notes for your reviewer:

[JamesLaverack]

/priority important-soon

[saschagrunert]

After this has been merged we should update the KEP:
https://github.com/kubernetes/enhancements/tree/master/keps/sig-release/2572-release-cadence

cc @kubernetes/sig-release-leads

[jeremyrickard]

After this has been merged we should update the KEP: https://github.com/kubernetes/enhancements/tree/master/keps/sig-release/2572-release-cadence

cc @kubernetes/sig-release-leads

I think we just messed up in the table. The KEP policy says:

The first Kubernetes release of a year should start at the second or third week of January to provide people more room after coming back from the Christmas holidays.

Which is what you mentioned above, so we should update the dates in there to reflect. I'll open a PR to do that.

[JamesLaverack]

From that KEP:

This would result in a 15 week release cycle, with 2 weeks between release cycles.

If we started with Monday 10th January 2022 as our Week 1, then the release would be on Tuesday 19th April.

That would mean that 1.25 would have to start two weeks later on Monday 9th May and release on Tuesday 16th August, and 1.26 starts on Monday 5th September and release on Tuesday 13th December. Does that sound about right?

[saschagrunert]

From that KEP:

This would result in a 15 week release cycle, with 2 weeks between release cycles.

If we started with Monday 10th January 2022 as our Week 1, then the release would be on Tuesday 19th April.

That would mean that 1.25 would have to start two weeks later on Monday 9th May and release on Tuesday 16th August, and 1.26 starts on Monday 5th September and release on Tuesday 13th December. Does that sound about right?

Yep.

[saschagrunert]

/hold
for EA review
/assign @jrsapi

[jrsapi]

Just waiting on the last lead to be entered.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JamesLaverack, jrsapi, saschagrunert

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• releases/OWNERS [saschagrunert]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[JamesLaverack]

/unhold
Unheld after discussion with @jrsapi offline

[reylejano]

non-blocking nit because this PR is for the outline but in the TL;DR v1.24.0 is released in week 15 and this suggestion aligns the timeline with the TL;DR for the v1.24.0 release during week 15.
Also suggest to add publishing the "Deprecations and Removals blog" per 1.22 and 1.23 retros to the timeline.

Suggested change

	| Burndown Meetings daily| Lead | **TBC** | week 13 | |
	| **Begin [Code Freeze]** (**Time TBC**) | Branch Manager | **TBC** | week 13 | |
	| 1.24.0-beta.0 released | Branch Manager | **TBC** | week 13 | |
	| Docs deadline - Open placeholder PRs | Docs Lead | **TBC** | week 13 | |
	| **[Test Freeze]** (**Time TBC**) | Branch Manager | **TBC** | week 14 | |
	| Docs deadline - PRs ready for review | Docs Lead | **TBC** | week 14 | |
	| 1.24.0-rc.0 released | Branch Manager | **TBC** | week 14 | |
	| release-1.24 branch created | Branch Manager | **TBC** | week 14 | |
	| release-1.24 jobs created | Branch Manager | **TBC** | week 14 | |
	| Start final draft of Release Notes | Release Notes Lead | **TBC** | week 14 | |
	| Release blog ready to review (**Time TBC**) | Comms / Docs | **TBC** | week 14 | |
	| Docs complete - All PRs reviewed and ready to merge | Docs Lead | **TBC** | week 15 | |
	| Feature blogs ready to review (**Time TBC**)| Enhancement Owner / SIG Leads | **TBC** | week 15 | |
	| Release Notes complete - reviewed & merged to `k/sig-release` (**Time TBC**) | Release Notes Lead | **TBC** | week 15 | |
	| 1.24.0-rc.1 released | Branch Manager | **TBC** | week 15 | |
	| **v1.24.0 released** | Branch Manager | **TBC** | week 16 | |
	| Release blog published | Comms | **TBC** | week 16 | |
	| **[Thaw]** | Branch Manager | **TBC** | week 16 | |
	| Release retrospective part 2 (**TBC**) | Community | **TBC** | week 17 | |
	| Release retrospective part 3 (**TBC**) | Community | **TBC** | week 17 | |
	| Burndown Meetings daily| Lead | **TBC** | week 12 | |
	| **Begin [Code Freeze]** (**Time TBC**) | Branch Manager | **TBC** | week 12 | |
	| 1.24.0-beta.0 released | Branch Manager | **TBC** | week 12 | |
	| Docs deadline - Open placeholder PRs | Docs Lead | **TBC** | week 12 | |
	| Deprecations and Removals blog published | Comms | **TBC** | week 12 | |
	| **[Test Freeze]** (**Time TBC**) | Branch Manager | **TBC** | week 13 | |
	| Docs deadline - PRs ready for review | Docs Lead | **TBC** | week 13 | |
	| 1.24.0-rc.0 released | Branch Manager | **TBC** | week 13 | |
	| release-1.24 branch created | Branch Manager | **TBC** | week 13 | |
	| release-1.24 jobs created | Branch Manager | **TBC** | week 13 | |
	| Start final draft of Release Notes | Release Notes Lead | **TBC** | week 13 | |
	| Release blog ready to review (**Time TBC**) | Comms / Docs | **TBC** | week 13 | |
	| Docs complete - All PRs reviewed and ready to merge | Docs Lead | **TBC** | week 14 | |
	| Feature blogs ready to review (**Time TBC**)| Enhancement Owner / SIG Leads | **TBC** | week 14 | |
	| Release Notes complete - reviewed & merged to `k/sig-release` (**Time TBC**) | Release Notes Lead | **TBC** | week 14 | |
	| 1.24.0-rc.1 released | Branch Manager | **TBC** | week 14 | |
	| **v1.24.0 released** | Branch Manager | **TBC** | week 15 | |
	| Release blog published | Comms | **TBC** | week 15 | |
	| **[Thaw]** | Branch Manager | **TBC** | week 15 | |
	| Release retrospective part 2 (**TBC**) | Community | **TBC** | week 16 | |
	| Release retrospective part 3 (**TBC**) | Community | **TBC** | week 16 | |

[JamesLaverack]

This is a great shout. I've made this into commit 5df623d on my follow-up PR #1798 to add the full schedule.

[reylejano]

My non-blocking nit and comment can be addressed in a follow-up PR
/lgtm

[jrsapi]

/LGTM