Initial v1.31 docs

[neoaggelos]

What type of PR is this:

/kind documentation

What this PR does / why we need it:

Adding initial documentation for v1.30 release and to discuss the potential release timeline.

Which issue(s) this PR fixes:

References #2493

Special notes for your reviewer:

cc @Priyankasaggu11929 @gracenng @katcosgrove

[Priyankasaggu11929]

cc: @kubernetes/sig-release-leads

[leonardpahlke]

Did we discuss the timeline already? We may want to wait a few days for feedback.

cc @dims @liggitt

[saschagrunert]

How about omitting v1.31.0-rc.2 and shifting everything into the last week of August? This would give v1.32 one more week, which is already a short one due to holidays.

[dims]

+1 We definitely need to pull things in by at least a week please. All the previous 2nd release of the year were 1.22, 1.25, 128 were in August - looking at https://endoflife.date/kubernetes. If plan for Sep and we slip by a week that will make it hard for the last release of the year (fewer weeks there).

[dims]

Alternatively can start a week earlier like we did in 1.28? https://github.com/kubernetes/sig-release/blob/fc1b3f7229ed78dccaf5271fb26c6c5c5b8b1feb/releases/release-1.28/README.md

[liggitt]

+1, early-to-mid-August is where we've targeted in the past

[liggitt]

for reference, here are historical release targets since 1.19 when we moved to 3 releases a year

The mid-year target release date has ranged from August 4th - August 25th, with an average of August 17th.

[neoaggelos]

i've moved start to 20th may and release to august 22nd. @Priyankasaggu11929 do you think there would be enough time to handle the shadow applications if we started on the week of 13th may? I will be mostly unavailable during week 1, but we could still start I think

[katcosgrove]

Moving the start of the release to 20 May with a 22 August target for release is reasonable to me. That gives us enough time to run the shadow application and selection process, with a nice gap for 1.32. Pulling it any earlier than that will cut into shadow selection, but week 0 and week 1 are both so light for most teams it's doable if necessary.

[Priyankasaggu11929]

I've moved start to 20th may and release to august 22nd. @Priyankasaggu11929 do you think there would be enough time to handle the shadow applications if we started on the week of 13th may?

I can send 1.31 shadow application form, as soon as tomorrow (May 1), run it for for 2 weeks (till May 15), and then announce/inform all applicants by May 22 at max.

So, starting as early as August May 13/14/15 should be fine IMO. We could then just use the first week to kick-off 1.31 enhancements opt-in, while we conclude selections.

For sending out shadow application, I need a start date & tentative target release date, to inform applicants of their required time commitments.

[katcosgrove]

Do you mean starting May 13? I'm okay with that schedule, Week 1 doesn't have work for shadows (usually).

[dims]

thanks @neoaggelos @Priyankasaggu11929 @katcosgrove

[justaugustus]

/hold for signoff from subproject leads: @gracenng @katcosgrove

[katcosgrove]

Thanks for adjusting the start and end dates! I'm happy with this.

/unhold
/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: neoaggelos, 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