Enhancements handbook updates #2932
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
k8s-ci-robot
added
do-not-merge/work-in-progress
k8s-ci-robot
added
cncf-cla: yes
k8s-ci-robot
added
do-not-merge/contains-merge-commits
size/XXL
jenshu
commented
Jan 30, 2026
| - [ ] KEP status is marked as `implementable` for `latest-milestone: { CURRENT_RELEASE }`. | ||
| - [ ] KEP readme has up-to-date graduation criteria. | ||
| - [ ] KEP has a production readiness review that has been completed and merged into k/enhancements. (For more information on the PRR process, check [here](https://github.com/kubernetes/community/blob/master/sig-architecture/production-readiness.md#submitting-a-kep-for-production-readiness-approval)). | ||
| - [ ] There are no other outstanding (unmerged) PRs that modify the KEP readme or kep.yaml file. |
Contributor
Author
There was a problem hiding this comment.
this checkbox is new
| - [X] KEP readme has up-to-date graduation criteria. | ||
| - [X] KEP has [submitted a production readiness review](https://github.com/kubernetes/community/blob/master/sig-architecture/production-readiness.md#submitting-a-kep-for-production-readiness-approval) request for approval and has a reviewer assigned. | ||
| - [X] KEP has a production readiness review that has been completed and merged into k/enhancements. (For more information on the PRR process, check [here](https://github.com/kubernetes/community/blob/master/sig-architecture/production-readiness.md#submitting-a-kep-for-production-readiness-approval)). | ||
| - [X] There are no other outstanding (unmerged) PRs that modify the KEP readme or kep.yaml file. |
Contributor
Author
There was a problem hiding this comment.
this checkbox is new
|
|
||
| If you still wish to progress this enhancement in {current release}, please file an [exception](https://github.com/kubernetes/sig-release/blob/master/releases/EXCEPTIONS.md) request as soon as possible, within three days. If you have any questions, you can reach out in the #release-enhancements channel on Slack and we'll be happy to help. Thanks! | ||
|
|
||
| /remove-label tracked/yes |
Contributor
Author
There was a problem hiding this comment.
added this to clear out the existing tracked label
|
|
||
| If you still wish to progress this enhancement in {current release}, please file an [exception](https://github.com/kubernetes/sig-release/blob/master/releases/EXCEPTIONS.md) request as soon as possible, within three days. If you have any questions, you can reach out in the #release-enhancements channel on Slack and we'll be happy to help. Thanks! | ||
|
|
||
| /remove-label tracked/yes |
Contributor
Author
There was a problem hiding this comment.
added this to clear out the existing tracked label
| - List of members for this group is managed in git. Create a [pull request](https://github.com/kubernetes/k8s.io/pull/1533) against [kubernetes/k8s.io](https://github.com/kubernetes/k8s.io/) repo to include both Lead and Shadows under `release-team` group in [k8s.io/sig-release/group.yaml](https://github.com/kubernetes/k8s.io/blob/bd082f195599b8a86b76b0249e5f70f219f1d079/groups/sig-release/groups.yaml#L318) | ||
| - MUST be a member of the [SIG Release Google Group][sig-release-group] | ||
| - MUST be a member of the [SIG Architecture Google Group][sig-arch-group] | ||
| - MUST be a member of the [Kubernetes Enhancements Google Group][enhancements-group] |
Contributor
Author
There was a problem hiding this comment.
as far as i can tell, this group is not used so i removed it from the requirements
| #### Why check for untracked user-facing features | ||
| | Status | Description | | ||
| |-----------------------:|---------------------------------------------------------------------------------------------------------------------------------------------| | ||
| | Tracked For PRR Freeze | Enhancement has met all PRR Freeze requirements for inclusion into current release. | |
Contributor
Author
There was a problem hiding this comment.
added the PRR Freeze statuses and updated some of the text below
|
|
||
| # Code Freeze Exceptions requested in v1.35 | ||
| During the meeting: | ||
| - Unhold (`/unhold`) the PR enforcing code freeze, allowing it to merge. This will prevent any PRs from merging unless they are in the current milestone. |
Contributor
Author
There was a problem hiding this comment.
these Code Freeze Party steps were added
| - Cleanup old milestones | ||
| - Open a pull request to add the exceptions.yaml file with all the KEPs which applied for an exception during enhancements freeze and code freeze. You can find an example of this exceptions.yaml file [here](https://github.com/kubernetes/sig-release/blob/master/releases/release-1.29/exceptions.yaml). | ||
|
|
||
| ### Limitations |
Contributor
Author
There was a problem hiding this comment.
moved to the Process section above
|
|
||
| It is important that this process be followed and documentation remain up-to-date as the [Enhancements repo][k/enhancements] is the primary ingress point for contributors interested in tracking enhancements. | ||
|
|
||
| ### Milestone Activities + Timing |
Contributor
Author
There was a problem hiding this comment.
moved this section to below the Process section
jenshu
changed the title
Contributor
Author
k8s-ci-robot
removed
the
do-not-merge/work-in-progress
jmickey
reviewed
Feb 2, 2026
|
|
||
| If the Enhancement Issue **does** meet the enhancement freeze criteria for inclusion in the current release (and has not already been marked as `Tracked for enhancements freeze`), use this template in Issue comments: | ||
| ### Week of Enhancements Freeze | ||
| - Schedule an "Enhancements Freeze Party" for the day of the Enhancements Freeze. Invite all the Enhancement shadows, Emeritus Advisor, Release Team Lead and Lead Shadows (make participation optional for the invitees due to potential timezone differences.) Post the "Enhancements Freeze Party" meeting details in the #sig-release and #release-enhancements Kubernetes Slack channels. **Note**: It is helpful to delegate enhancements to review to shadows to help with the process. |
Member
There was a problem hiding this comment.
Suggested change
| - Schedule an "Enhancements Freeze Party" for the day of the Enhancements Freeze. Invite all the Enhancement shadows, Emeritus Advisor, Release Team Lead and Lead Shadows (make participation optional for the invitees due to potential timezone differences.) Post the "Enhancements Freeze Party" meeting details in the #sig-release and #release-enhancements Kubernetes Slack channels. **Note**: It is helpful to delegate enhancements to review to shadows to help with the process. | |
| - Schedule an "Enhancements Freeze Party" for the day of the Enhancements Freeze. Invite all the Enhancement shadows, Subproject Leads, Release Team Lead and Lead Shadows (make participation optional for the invitees due to potential timezone differences.) Post the "Enhancements Freeze Party" meeting details in the #sig-release and #release-enhancements Kubernetes Slack channels. **Note**: It is helpful to delegate enhancements to review to shadows to help with the process. |
Member
|
/lgtm I suggested a small change. As you said there are definitely other areas that need to be updated, especially now that PRR Freeze is a hard deadline (e.g. Enhancements board sync should be disabled at the PRR freeze deadline instead of enhancements freeze), but these can be raised in a separate PR. |
k8s-ci-robot
added
the
lgtm
Member
|
/approve Not sure if I'd have the approval right, just trying with hold as well |
k8s-ci-robot
added
do-not-merge/hold
Contributor
Author
|
I'll let this merge and open a follow-up PR with further changes (including addressing any PR comments from this one) /unhold |
k8s-ci-robot
removed
the
do-not-merge/hold
jenshu
force-pushed
the
enhancement-handbook-updates-2
branch
from
420ebd2 to
94e2e23
Compare
Contributor
|
New changes are detected. LGTM label has been removed. |
k8s-ci-robot
removed
the
lgtm
jenshu
force-pushed
the
enhancement-handbook-updates-2
branch
from
94e2e23 to
44235ba
Compare
Contributor
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: jenshu, rytswd The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
k8s-ci-robot
removed
the
approved
Contributor
Author
|
sorry, messed up the rebase. Use #2952 instead |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this:
/kind documentation
What this PR does / why we need it:
The Release Enhancements handbook was getting a bit unwieldy with lots of info, so moved some things around to make it easier to navigate:
Processsection to make theMilestone Activities + Timingmore easy to follow.Also some fixes and retros items:
Which issue(s) this PR fixes:
None
Special notes for your reviewer:
There is further cleanup that can be done, but didn't want to have too many moving parts at once.
I added PR comments to sections that have changed, to make it easier to review.
Since a lot of sections were just moved around, it's hard to review the diff and might be better just to read the updated version of the readme