[NOTICE] Reminder for Code Freeze 1.18 Thursday, March 05, 2020

[jorge alarcon]

Hello Kubernetes community :-)

This is a friendly reminder that code freeze for Kubernetes 1.18 is NEXT THURSDAY.

And docs Placeholder PRs are due THIS FRIDAY February 28.

Documentation wise, please make sure your enhancements have open placeholder PRs for tracking and updating purposes.

This is a prerequisite for completing your feature work.

Ask in #sig-release if you need assistance, @Vineeth and the docs team will be able to help you.

Other than that, please prioritize all work you want to complete for Kubernetes 1.18 and make sure you have it in a merge-able state by code freeze.

For more information about the 1.18 schedule, please visit https://github.com/kubernetes/sig-release/tree/master/releases/release-1.18.

And if you have any questions or need help with anything, please reach out via slack on #sig-release, respond to this post, or you can find me

on slack as @alejandrox1.

Happy Kubernetes-ing and thank you for the work you all do!

Jorge Alarcon Ochoa, Release Lead for 1.18

[Stephen Augustus]

A clarifying note, since we're getting some questions in #sig-release.

Mechanically, Code Freeze starts whenever the change to the Prow config merges, which has already happened.

As the Release Managers group is geographically diverse, this PR may be created and merged ahead of EOD PT, which is the time we've classically done Code Freeze.

For reviewers/approvers/milestone maintainers --

• Today: Ensure PRs are milestoned and approved (lgtm+approve) by EOD PT
• Tomorrow (and for cycle duration): Only release-blocking PRs should be approved for milestone
  

We'll work on improved documentation for the release phases and timing moving into next cycle.

-- Stephen

On Thu, Mar 5, 2020 at 2:17 PM Carlos Tadeu Panato Jr <cta...@gmail.com> wrote:

Hello Kubernetes community :-)

Just to let y'all know that we are now in Code Freeze!

For more info about code freeze, you can check this https://github.com/kubernetes/sig-release/blob/master/releases/release_phases.md#code-freeze

And for more information about the 1.18 schedule, please visit https://github.com/kubernetes/sig-release/tree/master/releases/release-1.18.

And if you have any questions or need help with anything, please reach out via slack on #sig-release, respond to this post, or you can find me

on slack as @cpanato or our Release Lead for 1.18 @alejandrox1 

 Thank you for the work you all do!

Carlos Panato

--
You received this message because you are subscribed to the Google Groups "Kubernetes developer/contributor discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-dev/fce67aaa-35bb-40bc-8c2d-dccd661d5a48%40googlegroups.com.