Skip to content

Enhancements handbook updates: tracking board and beginning/end of release steps#2992

Merged
k8s-ci-robot merged 6 commits into
kubernetes:masterfrom
jenshu:enhancements-handbook-tracking-board
May 19, 2026
Merged

Enhancements handbook updates: tracking board and beginning/end of release steps#2992
k8s-ci-robot merged 6 commits into
kubernetes:masterfrom
jenshu:enhancements-handbook-tracking-board

Conversation

@jenshu
Copy link
Copy Markdown
Contributor

@jenshu jenshu commented Apr 9, 2026

What type of PR is this:

/kind documentation

What this PR does / why we need it:

  • Add steps for cleaning up and setting up the tracking board
  • Update the beginning of release (week 0-2) and end of the release tasks

Which issue(s) this PR fixes:

N/A

Special notes for your reviewer:

@k8s-ci-robot k8s-ci-robot added kind/documentation Categorizes issue or PR as related to documentation. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-priority labels Apr 9, 2026
@k8s-ci-robot k8s-ci-robot requested a review from aibarbetta April 9, 2026 03:51
@k8s-ci-robot k8s-ci-robot added the area/release-team Issues or PRs related to the release-team subproject label Apr 9, 2026
@k8s-ci-robot k8s-ci-robot requested a review from jmickey April 9, 2026 03:51
@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 Apr 9, 2026
@jenshu jenshu requested review from dipesh-rawat and rayandas and removed request for aibarbetta April 9, 2026 03:51

#### Meeting update rotation

- Create a Google Sheet (private to the Enhancements Lead and Shadows) where the shadows can sign up to give updates at the weekly Release Team meetings.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

thanks! added in 6ceea98

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Who owns this google doc? Not sure we should link external content that is outside Kubernetes community control. Could we create a Markdown version of this template instead?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

moved to to a markdown template and adjusted instructions 318f973


### Succession
- The Enhancements Lead may be called upon by the Communications Lead to help with media engagement near the end of the release cycle. Please ensure that if there are any restrictions or training required by your company before engaging that you have completed those ahead of Code Thaw.
- After the release, the Enhancements Lead will participate in a livestreamed CNCF Kubernetes Release webinar along with the Release Lead and Communications Lead. Work together to prepare a presentation highlighting a selection of enhancements from this release.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Should we include a link to a previous release webinar?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

good idea. I couldn't find a playlist with all of them, so I just linked to the last few 6ceea98

Copy link
Copy Markdown
Member

@dipesh-rawat dipesh-rawat left a comment

Choose a reason for hiding this comment

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

Overall, the updates look good. I have added a few small comments that should be easy to address and get this merged by this week.


#### Update tracking board documentation

Note: the Release Lead sometimes opens a single PR with the updates for all the subteams; sync with them to avoid duplicate work.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

This note feels a bit out of place here, or I may be missing something.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

removed in 318f973


#### Meeting update rotation

- Create a Google Sheet (private to the Enhancements Lead and Shadows) where the shadows can sign up to give updates at the weekly Release Team meetings.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Who owns this google doc? Not sure we should link external content that is outside Kubernetes community control. Could we create a Markdown version of this template instead?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Might be overthinking here but if we make end of release cleanup the standard process, some of the template wordings may need a small tweak. Not sure what everyone feels about it.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Last release, we used something like:

Hi <kep-contributor> 👋, 1.xx Enhancements Team here.

We are nearing the close of the v1.xx release. As part of cleanup, we are removing the `lead-opted-in` label and clearing the milestone.

If you would like this considered for the next release, please have the SIG lead opt in again by re-adding the label and setting the new milestone.

Thanks!

/remove-label lead-opted-in
/milestone clear

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

reworded in f33e476

@k8s-ci-robot
Copy link
Copy Markdown
Contributor

@dipesh-rawat: The label(s) /remove-label lead-opted-in cannot be applied. These labels are supported: api-review, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, team/katacoda, refactor, ci-short, ci-extended, ci-full. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

Details

In response to this:

Last release, we used something like:

Hi <kep-contributor> 👋, 1.xx Enhancements Team here.

We are nearing the close of the v1.xx release. As part of cleanup, we are removing the `lead-opted-in` label and clearing the milestone.

If you would like this considered for the next release, please have the SIG lead opt in again by re-adding the label and setting the new milestone.

Thanks!

/remove-label lead-opted-in
/milestone clear

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-sigs/prow repository.

@k8s-ci-robot k8s-ci-robot added size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. and removed size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels May 18, 2026
- [Code Freeze Templates](#code-freeze-templates)
- [Code Freeze Party Templates](#code-freeze-party-templates)

## SIG Outreach Templates
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

this was moved into the new file sig-outreach-assignment-template.md


We will rotate the person giving updates at each Release Team meeting. Please sign up for 3-5 slots in the timezone that works for you!

<table style="border-collapse: collapse; width: 100%;">
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

had to use html instead of markdown to get the colspan=4 rows looking right. interestingly if you copy and paste into a google doc as 'markdown' it works!

Copy link
Copy Markdown
Member

@dipesh-rawat dipesh-rawat left a comment

Choose a reason for hiding this comment

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

Thanks for making these changes. They are really useful and much needed.

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label May 18, 2026
@rayandas
Copy link
Copy Markdown
Member

Thanks for the changes Jenny.
/lgtm

@jmickey
Copy link
Copy Markdown
Member

jmickey commented May 19, 2026

Great improvement!

/lgtm
/approve

@k8s-ci-robot
Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dipesh-rawat, jenshu, jmickey

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details 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

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 19, 2026
@k8s-ci-robot k8s-ci-robot merged commit 44eb151 into kubernetes:master May 19, 2026
2 checks passed
@k8s-ci-robot k8s-ci-robot added this to the v1.37 milestone May 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. 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. needs-priority sig/release Categorizes an issue or PR as relevant to SIG Release. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants