-
Notifications
You must be signed in to change notification settings - Fork 404
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.
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
Create 1.33 release directory #2706
Create 1.33 release directory #2706
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some comments on board observation and column naming:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A couple of comments tied with the v1.32 experience.
| Deprecations and Removals blog published | Comms | Monday 24th March 2025 | week 11 | | | ||
| **Preparing for Feature blogs review — Initiating outreach** | Comms | Monday 24th March 2025 | week 11 | | | ||
| Docs deadline — PRs ready for review | Docs Lead | Tuesday 25th March 2025 | week 11 | | | ||
| Release Highlights deadline | Comms | Tuesday 25th March 2025 | week 11 | | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mbianchidev @rytswd Updated the Release Highlights deadline
to be before Release blog ready to review
based on https://kubernetes.slack.com/archives/C2C40FMNF/p1736496690555129?thread_ts=1735581655.943799&cid=C2C40FMNF. Let me know how this looks like from the Comms perspective.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
could you please a timezone link for our major deadline in a following PR
@Vyom-Yadav could you please remove your change request? |
Does that prevent a PR from merging? I thought prow did it irrespective of whether a 'requested changes' is pending. |
I think this needs an approval from someone in @kubernetes/sig-release-leads to merge |
/approve |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: gracenng, katcosgrove, npolshakova, Vyom-Yadav The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Dang, though I had the perms for this. /assign @jeremyrickard |
What type of PR is this:
/kind documentation
What this PR does / why we need it:
Creates the 1.33 release directory as per #2705
Which issue(s) this PR fixes:
None
Special notes for your reviewer: