[ANNOUNCEMENT] Release v1.21 Branch Creation and Merge Requirements

28 views
Skip to first unread message

Marko Mudrinić

unread,
Mar 29, 2021, 12:30:34 PM3/29/21
to Kubernetes developer/contributor discussion, le...@kubernetes.io, kubernetes-sig-release, releas...@kubernetes.io

Hello everyone!


We’re happy to announce that the release-1.21 branch has been created on Friday, March 27th. This is a step forward to the final release which is scheduled for April 8th.


With the release branch in-place, all PRs targeting the v1.21 release MUST be cherry-picked to the release-1.21 branch.


Considering that the code freeze is in the effect, only critical, release blocking PRs will be allowed to be merged. The workflow to get your PRs merged is the following:

  • Tag the Release Team Leads and the Release Managers on your PR to the master branch, such as: “/cc @kubernetes/release-managers @kubernetes/release-team-leads”

  • Provide a short description of why you think that your PR is release blocking

  • The Release Team Lead will review your PR and apply the v1.21 milestone if it qualifies as a release blocking PR

  • Once your PR is merged to the master branch, create a cherry-pick to the release-1.21 branch. Check out the following document to find out how to create a cherry-pick: https://git.k8s.io/community/contributors/devel/sig-release/cherry-picks.md

  • Ensure that the cherry-pick PR has approved and lgtm labels. Once those labels are in place, tag the Release Team Leads and the Release Managers on your cherry-pick PR (“/cc @kubernetes/release-managers @kubernetes/release-team-leads”).


If you have any questions, please reach out to the SIG Release on the #sig-release Slack channel.


Best regards,

Marko Mudrinić, Release Manager

Reply all
Reply to author
Forward
This conversation is locked
You cannot reply and perform actions on locked conversations.
0 new messages