📖 Update v1.10 release cycle schedule

[mboersma]

What this PR does / why we need it:

Updates the release-v1.10.md doc to compress the v1.10 schedule in order to accomodate an earlier code freeze and v1.11/v1beta2 schedule.

Which issue(s) this PR fixes:

Refs #11656

/area release

[mboersma]

/cc @fabriziopandini

[sbueringer]

/assign @fabriziopandini
for a first round

[cprivitere]

/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 83fd6e9e8f3e82597158d485e6241c895d32e994

[fabriziopandini]

What about if we keep the release schedule as it is and we just move:

| release-1.10 branch created (**Begin [Code Freeze]**)| Release Lead | Tuesday 8nd 
April 2025 | week 14 |

from week 14 to week 11, right before v1.10.0-beta.0 released the 18th of March?

Index: docs/release/releases/release-1.10.md
IDEA additional info:
Subsystem: com.intellij.openapi.diff.impl.patch.CharsetEP
<+>UTF-8
===================================================================
diff --git a/docs/release/releases/release-1.10.md b/docs/release/releases/release-1.10.md
--- a/docs/release/releases/release-1.10.md	(revision ddedb239945112ac336e765987016a3e5536c8cf)
+++ b/docs/release/releases/release-1.10.md	(date 1737386720553)
@@ -11,12 +11,12 @@
 | Team finalized                                       | Release Lead | Friday 10 January 2025      | week 1   |
 | *v1.8.x & v1.9.x released*                           | Release Lead | Tuesday 21th January 2025   | week 3   |
 | *v1.8.x & v1.9.x released*                           | Release Lead | Tuesday 18th February 2025  | week 7   |
+| release-1.10 branch created (**Begin [Code Freeze]**)| Release Lead | Tuesday 18th March 2025     | week 11  |
 | v1.10.0-beta.0 released                              | Release Lead | Tuesday 18th March 2025     | week 11  |
 | Communicate beta to providers                        | Comms Manager| Tuesday 18th March 2025     | week 11  |
 | *v1.8.x & v1.9.x released*                           | Release Lead | Tuesday 18th March 2025     | week 11  |
 | v1.10.0-beta.x released                              | Release Lead | Tuesday 25th March 2025     | week 12  |
 | KubeCon idle week                                    |      -       | 1st - 4th April 2025        | week 13  |
-| release-1.10 branch created (**Begin [Code Freeze]**)| Release Lead | Tuesday 8nd April 2025      | week 14  |
 | v1.10.0-rc.0 released                                | Release Lead | Tuesday 8nd April 2025      | week 14  |
 | release-1.10 jobs created                            | CI Manager   | Tuesday 8nd April 2025      | week 14  |
 | v1.10.0-rc.x released                                | Release Lead | Tuesday 15th April 2025     | week 15  |

This will minimize the impact on the release team/on the community (everything else remain the same except for the date when we create the release branch/code freeze)?

[mboersma]

What about if we keep the release schedule as it is and we just move...

That's fine with me. I thought we wanted to compress the whole v1.10 schedule after that. But if we're ok with a long time between v1.10-beta.0 and release, we can just move the branch creation / code freeze date back three weeks and leave everything else as it was.

[sbueringer]

Agree with Fabrizio. We also want to support Kubernetes 1.33 in our .1 release ideally. And their release date is 23rd April

[fabriziopandini]

Thanks for this PR!
/lgtm
/approve

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 257ae1757945a289bb91dacac76e83874cd1b2f3

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fabriziopandini

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:

• docs/release/OWNERS [fabriziopandini]

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

[sbueringer]

We should move this line as well. Otherwise we don't have tests on release-1.10 for 3 weeks

[fabriziopandini]

#11799