[Please read] KEP-2853: Kubernetes repository branch rename

[Carlos Tadeu Panato Jr]

KEP-2853: Kubernetes repository branch rename

In the Kubernetes and wider CNCF community, there is an effort to make all the language and terms more inclusive. One small step towards this goal is to change the default branch name of the kubernetes/kubernetes repository from master to main, which is more inclusive and less negatively influenced.

Per our KEP-2853, we did a survey, and the answers we collected were that the downstream users need a few weeks to prepare for this change.

We are planning the branch rename when we reach code freeze for the 1.25 release, which the scheduled date is 01:00 UTC Wednesday 3rd August 2022 (code freeze), and then do the branch rename on Monday 3rd August 2022.

Check the 1.25 calendar https://github.com/kubernetes/sig-release/tree/master/releases/release-1.25#timeline

Let us know if you have any questions.

All the best

Carlos

- on behalf of SIG Release

[Rodrigo Campos]

On 7/26/22 09:57, Carlos Tadeu Panato Jr wrote:
>
> We are planning the branch rename when we reach code freeze for the 1.25
> release, which the scheduled date is 01:00 UTC Wednesday 3rd August 2022
> (code freeze), and then do the branch rename on Monday 3rd August 2022.

The bran rename is next Monday? Then Monday August 8th?



Best,
Rodrigo

[Carlos Tadeu Panato Jr]

UPDATE:

The proposed date to rename is Monday 8th August 2022 and not the 3rd as mentioned in the original email, sorry for the inconvenience caused and thanks for Rodrigo for the catch.

--
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/d3e6d30f-ddfe-0d29-adef-68615ad98fcc%40sdfg.com.ar.

[Carlos Tadeu Panato Jr]

Hello Kubernetes Community!

After some discussions regarding the branch rename, we have decided to postpone this change to the next cycle (v1.26).
We will send more communication regarding this change and update the KEP to reflect the updates.

Thanks so much for your attention and work!

All the best

Carlos

- on behalf of SIG Release