Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Freeze k/website for Kubernetes 1.26 release #38317

Closed
krol3 opened this issue Dec 7, 2022 · 3 comments
Closed

Freeze k/website for Kubernetes 1.26 release #38317

krol3 opened this issue Dec 7, 2022 · 3 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. sig/release Categorizes an issue or PR as relevant to SIG Release. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@krol3
Copy link
Contributor

krol3 commented Dec 7, 2022

This issue is for freezing the k/website for the Kubernetes 1.26 release.

The release is scheduled to happen tomorrow (Thursday 8th December 2022) and No PRs are allowed to merge until the release PR has successfully merged.

If there are any questions, please contact me or anyone from the docs release team

cc: @reylejano @onlydole @divya-mohan0209 @jimangel @natalisucks
cc: @cathchu @mickeyboxell @katmutua @Rishit-dagli

/sig release
/label tide/merge-blocker
@krol3 krol3 added the kind/feature Categorizes issue or PR as related to a new feature. label Dec 7, 2022
@k8s-ci-robot
Copy link
Contributor

@krol3: The label(s) /label tide/merge-blocker cannot be applied. These labels are supported: api-review, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, team/katacoda, refactor. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

In response to this:

This issue is for freezing the k/website for the Kubernetes 1.26 release.

The release is scheduled to happen tomorrow (Thursday 8th December 2022) and No PRs are allowed to merge until the release PR has successfully merged.

If there are any questions, please contact me or anyone from the docs release team

cc: @reylejano @onlydole @divya-mohan0209 @jimangel @natalisucks
cc: @cathchu @mickeyboxell @katmutua @Rishit-dagli

/sig release
/label tide/merge-blocker

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@k8s-ci-robot k8s-ci-robot added sig/release Categorizes an issue or PR as relevant to SIG Release. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Dec 7, 2022
@onlydole onlydole added tide/merge-blocker Denotes an issue that blocks the tide merge queue for a branch while it is open. and removed tide/merge-blocker Denotes an issue that blocks the tide merge queue for a branch while it is open. labels Dec 7, 2022
@reylejano
Copy link
Member

/triage accepted

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Dec 8, 2022
@leonardpahlke leonardpahlke mentioned this issue Dec 9, 2022
Merged
@krol3 krol3 removed the tide/merge-blocker Denotes an issue that blocks the tide merge queue for a branch while it is open. label Dec 9, 2022
@krol3 krol3 closed this as completed Dec 9, 2022
@krol3 krol3 reopened this Dec 9, 2022
@onlydole onlydole added the tide/merge-blocker Denotes an issue that blocks the tide merge queue for a branch while it is open. label Dec 9, 2022
@krol3
Copy link
Contributor Author

krol3 commented Dec 10, 2022

/unhold

@krol3 krol3 removed the tide/merge-blocker Denotes an issue that blocks the tide merge queue for a branch while it is open. label Dec 10, 2022
@krol3 krol3 closed this as completed Dec 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature. sig/release Categorizes an issue or PR as relevant to SIG Release. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@onlydole @krol3 @k8s-ci-robot @reylejano