Skip to content

Add Comms progress tracking issue template, adjust Release Highlight template #2792

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
Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Add Comms progress tracking issue template, adjust Release Highlight template #2792

wants to merge 2 commits into from
+345 −10

Conversation

rytswd
Copy link
Member

@rytswd rytswd commented May 29, 2025

What type of PR is this:

/kind documentation

What this PR does / why we need it:

Update the Comms handbook with the most recent details, and correct any parts for easier review.

Which issue(s) this PR fixes:

Updates #2718

@k8s-ci-robot k8s-ci-robot added kind/documentation Categorizes issue or PR as related to documentation. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-priority area/release-team Issues or PRs related to the release-team subproject labels May 29, 2025
@k8s-ci-robot k8s-ci-robot added sig/release Categorizes an issue or PR as relevant to SIG Release. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels May 29, 2025
@rytswd rytswd marked this pull request as draft May 29, 2025 03:17
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

  • Mark this PR as fresh with /remove-lifecycle stale
  • Close this PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 27, 2025
@justaugustus
Copy link
Member

/assign @katcosgrove

@drewhagen
Copy link
Member

Double checking @rytswd
Do you think there is anything we want to amend for comms this cycle before they get into the thick of things?

Otherwise, we could hold off as I imagine shadows are reading the handbook soon. (could add some confusion)

@rytswd
Copy link
Member Author

rytswd commented Sep 22, 2025

We would probably want to update a bit as this was not fully done. I'm sure @aibarbetta has more to add.
I'll update as much as I can in the coming days, and will get Agus to review and add her additions as well.

@rytswd rytswd force-pushed the update-comms-handbook-based-on-v1-33-learnings branch from 364cc8c to 1871f0d Compare October 8, 2025 21:10
@rytswd
Copy link
Member Author

rytswd commented Oct 8, 2025

/retitle Add Comms progress tracking issue template, adjust Release Highlight template

@k8s-ci-robot k8s-ci-robot changed the title [WIP] Update Comms handbook and templates Add Comms progress tracking issue template, adjust Release Highlight template Oct 8, 2025
@rytswd rytswd marked this pull request as ready for review October 8, 2025 21:12
@k8s-ci-robot k8s-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Oct 8, 2025
@rytswd
Copy link
Member Author

rytswd commented Oct 8, 2025

@aibarbetta @graz-dev So long overdue, but here is the quick template update from my end. It would be great if you could take a look and see if it would make sense to get these template updates in place, or simply keep it as is.

CC @drewhagen

@drewhagen drewhagen self-requested a review October 13, 2025 00:15
aibarbetta
aibarbetta approved these changes Oct 14, 2025
View reviewed changes
Copy link
Member

@aibarbetta aibarbetta left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! I left some nits

release-team/role-handbooks/communications/templates/progress-tracking-issue.md

- TBC

## Week15: Release + Post Release Actions
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
## Week15: Release + Post Release Actions
## Week 15: Release + Post Release Actions

release-team/role-handbooks/communications/templates/progress-tracking-issue.md
For v1.33, the release is planned on **Wednesday 23rd April 2025**. At this point, there shouldn't be too much that we need to handle other than last minute juggling...

### For Lead
* [ ] Update the Release Announcement blog with the logo and release name!
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* [ ] Update the Release Announcement blog with the logo and release name!
* [ ] Update the Release Announcement blog with the logo and release name!
* [ ] Once the Release Announcement is published, post in #announcements

release-team/role-handbooks/communications/templates/progress-tracking-issue.md
### For Lead
* [ ] Start drafting the mid cycle sneak peek blog
- The initial draft can happen outside PR
- Previous Mid Cycle Blogs:: [v1.29](https://kubernetes.io/blog/2023/11/16/kubernetes-1-29-upcoming-changes/), [v1.30](https://kubernetes.io/blog/2024/03/12/kubernetes-1-30-upcoming-changes/), [v1.31](https://kubernetes.io/blog/2024/07/19/kubernetes-1-31-upcoming-changes/), [v1.32](https://kubernetes.io/blog/2024/11/08/kubernetes-1-32-upcoming-changes/)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Previous Mid Cycle Blogs:: [v1.29](https://kubernetes.io/blog/2023/11/16/kubernetes-1-29-upcoming-changes/), [v1.30](https://kubernetes.io/blog/2024/03/12/kubernetes-1-30-upcoming-changes/), [v1.31](https://kubernetes.io/blog/2024/07/19/kubernetes-1-31-upcoming-changes/), [v1.32](https://kubernetes.io/blog/2024/11/08/kubernetes-1-32-upcoming-changes/)
- Previous Mid Cycle Blogs: [v1.29](https://kubernetes.io/blog/2023/11/16/kubernetes-1-29-upcoming-changes/), [v1.30](https://kubernetes.io/blog/2024/03/12/kubernetes-1-30-upcoming-changes/), [v1.31](https://kubernetes.io/blog/2024/07/19/kubernetes-1-31-upcoming-changes/), [v1.32](https://kubernetes.io/blog/2024/11/08/kubernetes-1-32-upcoming-changes/)

release-team/role-handbooks/communications/templates/progress-tracking-issue.md

## Other Follow-up Actions and Notes

- We should make clarification on when the Feature Blog opt-in reach-outs to happen (it was a bit vague)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would use the same clarification as the Release Highlights:

With Enhancement freeze in effect (in week 5), start the Feature Blog opt-in reach-outs

We did that for v1.34 and it gave us some time to do a second reminder

release-team/role-handbooks/communications/templates/progress-tracking-issue.md
- Make sure all the templates use the consistent KEP referencing of something like: `[KEP-4974: Deprecate v1.Endpoints](https://kep.k8s.io/4974)`
- Document the version should be "v" prefixed
- Update the blog status field to prefix with some numbers (the current "ready for review", "review in progress", "ready to publish" are all so similar and hard to see which one's which...)
- When getting the placeholder blog PRs for Feature Blogs, we will need to get the KEP authors to come back to us in the KEP. There were a few blogs I only caught by going through the list of blog PRs, and it was quite manual.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All good points, but I'm not sure they belong in this template. Perhaps we could move them to a Debt/Suggestions section in release-team/role-handbooks/communications/README.md?

release-team/role-handbooks/communications/templates/progress-tracking-issue.md
- Make sure all the templates use the consistent KEP referencing of something like: `[KEP-4974: Deprecate v1.Endpoints](https://kep.k8s.io/4974)`
- Document the version should be "v" prefixed
- Update the blog status field to prefix with some numbers (the current "ready for review", "review in progress", "ready to publish" are all so similar and hard to see which one's which...)
- When getting the placeholder blog PRs for Feature Blogs, we will need to get the KEP authors to come back to us in the KEP. There were a few blogs I only caught by going through the list of blog PRs, and it was quite manual.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- When getting the placeholder blog PRs for Feature Blogs, we will need to get the KEP authors to come back to us in the KEP. There were a few blogs I only caught by going through the list of blog PRs, and it was quite manual.
- When getting the placeholder blog PRs for Feature Blogs, we will need to get the KEP authors to come back to us in the KEP. Additionally, monitor https://github.com/kubernetes/website/pulls on Feature Blog opt-in season, check with the author and use labels `sig/release` and `area/blog` to keep track of them.

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Oct 14, 2025
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: aibarbetta, rytswd
Once this PR has been reviewed and has the lgtm label, please ask for approval from katcosgrove. For more information see the Code Review Process.

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@bradmccoydev bradmccoydev Awaiting requested review from bradmccoydev

@fsmunoz fsmunoz Awaiting requested review from fsmunoz

@graz-dev graz-dev Awaiting requested review from graz-dev

@katcosgrove katcosgrove Awaiting requested review from katcosgrove

@drewhagen drewhagen Awaiting requested review from drewhagen

1 more reviewer

@aibarbetta aibarbetta aibarbetta approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

@aibarbetta aibarbetta

@katcosgrove katcosgrove

Labels

area/release-team Issues or PRs related to the release-team subproject cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/documentation Categorizes issue or PR as related to documentation. lgtm "Looks good to me", indicates that a PR is ready to be merged. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. needs-priority sig/release Categorizes an issue or PR as relevant to SIG Release. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

7 participants

@rytswd @k8s-triage-robot @justaugustus @drewhagen @k8s-ci-robot @aibarbetta @katcosgrove