-
Notifications
You must be signed in to change notification settings - Fork 393
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
Clarified PRR freeze and exceptions.yaml in enhancements handbook #2518
Clarified PRR freeze and exceptions.yaml in enhancements handbook #2518
Conversation
@@ -177,6 +177,8 @@ It is important that this process be followed and documentation remain up-to-dat | |||
- Send an email to [Kubernetes-Dev](https://groups.google.com/a/kubernetes.io/g/dev) that Enhancement freeze is coming and share current Enhancements status. Examples [1](https://groups.google.com/g/kubernetes-dev/c/-nTNtBBHL2Y/m/WfNzb_E1EAAJ). | |||
- Provide updates during release team meetings | |||
- Use the `KEPs by Stage` insight from the Enhancement Tracking Board ([example](https://github.com/orgs/kubernetes/projects/98/insights/3)) | |||
- Notify folks in [#prod-readiness](https://kubernetes.slack.com/archives/CPNHUMN74) about KEPs waiting for PRR reviews with the project board filtered for KEPs missing PRR assignees. |
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.
💯, pretty useful!
@sreeram-venkitesh, outside of this PR's scope, but a note: we should add the blurb about PRR freeze in this document too - https://github.com/kubernetes/sig-release/blob/master/releases/release_phases.md |
cc: @salehsedghpour |
@sreeram-venkitesh, could you please squash the commits also to two (one for each file change). Thanks! |
d78ee59
to
6a2cba2
Compare
@Priyankasaggu11929 I've squashed the commits into two, one for each file! PTAL! |
610f94d
to
d9120b3
Compare
@npolshakova I've made the changes, PTAL! |
@sreeram-venkitesh, just checking if it is ready for another round of review? 🙂 |
@Priyankasaggu11929 Yes please! |
@tjons @ArkaSaha30 @dipesh-rawat @mickeyboxell @prianna could you all please give a round of review, so we get it merged max by end of this week? Thanks! |
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.
Generally looks good to me! Couple questions and I agree with @Priyankasaggu11929's feedback - thanks for doing this @sreeram-venkitesh!
@Priyankasaggu11929 @tjons Please review the new changes! I want to get this merged before the next cycle starts! |
Other than my comment here #2518 (comment), rest LGTM! Thank you so much again for all the work, @sreeram-venkitesh. |
/lgtm /hold Thanks again, @sreeram-venkitesh 🙂 |
Thanks a lot! Will unhold once @tjons also confirms the changes from his end :) |
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!
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Priyankasaggu11929, sreeram-venkitesh, tjons The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/hold cancel |
What type of PR is this:
/kind documentation
What this PR does / why we need it:
This PR fixes two issues from #2375
Which issue(s) this PR fixes:
Fixes part of #2375
Special notes for your reviewer:
CC: @Priyankasaggu11929 @npolshakova