[ANNOUNCEMENT] v1.31 Code Freeze Deadline Moved to July 24th

[Angelos Kolaitis]

Hello, hello, hello, Kubernetes Community!

I wanted to reach out with regards to an important change in the timeline of the Kubernetes 1.31 release.

After discussion in #sig-release earlier this week, the release team has decided to move the Code Freeze deadline to July 24th. This is 2 weeks later from the original date (July 10th).

What does this mean for you?

This gives the Kubernetes community 2 more weeks (10 working days) of development time to finish the implementation of new features and tests.

What do you need to do?

Nothing! Please continue your great work and focus on making Kubernetes the best it can be!

If you are working on a feature that you believe is in danger of not being complete and reviewed before July 24th, you are encouraged to file a pre-emptive Exception request.

Are any other dates affected by this change?

• The mid-cycle blog has also been moved to July 18th. This is 1 week later than originally planned (July 11th), so that it is closer to the date of the Code Freeze.

• The Test Freeze deadline (July 31st) is not affected.

• The tentative v1.31.0 release date (August 13th) is also not affected.

Where can I see the full schedule for Kubernetes 1.31?

The full timeline for Kubernetes 1.31 can be found on GitHub.

If you need any clarification, please reach out to us in the #sig-release Slack channel.

Χαιρετε,

Angelos Kolaitis

1.31 Release Team Lead

[Davanum Srinivas]

Thanks Angelos and the Release Team!

--
You received this message because you are subscribed to the Google Groups "dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dev+uns...@kubernetes.io.
To view this discussion on the web visit https://groups.google.com/a/kubernetes.io/d/msgid/dev/d82621fd-4e5d-4b67-9b3e-3c0ef9118f75n%40kubernetes.io.

--

Davanum Srinivas :: https://twitter.com/dims

[Antonio Ojea]

Thanks to Angelos and the Release Team, this is really a great example
of collaboration between SIGs.

I want to highlight one important implication, the Test Freeze period
is back to 1 week, from July 24th to July 31st.
This is important, specially for the people that may not be familiar
with the Kubernetes release phases, because the Test Freeze phase [1]
is sometimes misunderstood: it is not used to add tests to features.

Please, let's ensure that our features include the corresponding tests
at the time of merging, avoid merging APIs or functional code first
and wait until later to add the tests.

[1]: https://github.com/kubernetes/sig-release/blob/master/releases/release_phases.md#test-freeze

> To view this discussion on the web visit https://groups.google.com/a/kubernetes.io/d/msgid/dev/CANw6fcE9dqCnPLYdJ%2BnV1SyPPoreMyYpHg6dT6hq7puxgzqvCA%40mail.gmail.com.