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

rytswd · 2025-05-29T03:17:10Z

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-triage-robot · 2025-08-27T03:51:29Z

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

justaugustus · 2025-09-14T02:45:05Z

/assign @katcosgrove

drewhagen · 2025-09-22T03:06:50Z

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 · 2025-09-22T13:55:22Z

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 · 2025-10-08T21:12:23Z

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

rytswd · 2025-10-08T21:15:02Z

@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

aibarbetta

LGTM! I left some nits

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

aibarbetta · 2025-10-14T01:05:35Z

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)


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

What do you mean by this exactly? You mean there should be a clear note about the Feature Blog opt-in reminder to take place right after enhancement freeze, so something around line#133?

aibarbetta · 2025-10-14T01:08:29Z

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.


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?

I think we can mention in the PR description for future enhancements, but drop all of these comments from the template. I'll get to that in a bit.

aibarbetta · 2025-10-14T01:15:59Z

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.


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.

I'm not sure what you meant by "season" here -- is that potentially a typo?

k8s-ci-robot · 2025-10-14T01:17:32Z

[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:

release-team/role-handbooks/communications/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

rytswd

Thanks for the review! Just left a few comments

rytswd · 2025-10-21T17:09:15Z

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.


I think we can mention in the PR description for future enhancements, but drop all of these comments from the template. I'll get to that in a bit.

rytswd · 2025-10-21T17:17:32Z

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.


I'm not sure what you meant by "season" here -- is that potentially a typo?

rytswd · 2025-10-21T17:23:28Z

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)


What do you mean by this exactly? You mean there should be a clear note about the Feature Blog opt-in reminder to take place right after enhancement freeze, so something around line#133?

Co-authored-by: Agustina Barbetta <[email protected]>

k8s-ci-robot · 2025-10-21T17:24:35Z

New changes are detected. LGTM label has been removed.

k8s-ci-robot requested review from bradmccoydev and fsmunoz May 29, 2025 03:17

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 marked this pull request as draft May 29, 2025 03:17

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

k8s-ci-robot assigned katcosgrove Sep 14, 2025

rytswd added 2 commits October 8, 2025 22:09

Add progress tracking issue template from v1.33

6549582

Update Release Highlight reachout template

1871f0d

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

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 marked this pull request as ready for review October 8, 2025 21:12

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

k8s-ci-robot requested review from graz-dev and katcosgrove October 8, 2025 21:12

drewhagen self-requested a review October 13, 2025 00:15

aibarbetta approved these changes Oct 14, 2025

View reviewed changes

k8s-ci-robot assigned aibarbetta Oct 14, 2025

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

rytswd commented Oct 21, 2025

View reviewed changes

Apply suggestions from code review

e8bfc2a

Co-authored-by: Agustina Barbetta <[email protected]>

k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Oct 21, 2025


		## 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)

	- 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.

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

Are you sure you want to change the base?

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

Conversation

rytswd commented May 29, 2025

What type of PR is this:

What this PR does / why we need it:

Which issue(s) this PR fixes:

Uh oh!

k8s-triage-robot commented Aug 27, 2025

Uh oh!

justaugustus commented Sep 14, 2025

Uh oh!

drewhagen commented Sep 22, 2025

Uh oh!

rytswd commented Sep 22, 2025

Uh oh!

rytswd commented Oct 8, 2025

Uh oh!

rytswd commented Oct 8, 2025

Uh oh!

aibarbetta left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

k8s-ci-robot commented Oct 14, 2025

Uh oh!

rytswd left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

k8s-ci-robot commented Oct 21, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

7 participants