Enhancements handbook updates: tracking board and beginning/end of release steps#2992
Conversation
|
|
||
| #### 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. |
There was a problem hiding this comment.
I have an example template here: https://docs.google.com/document/d/1jfU34qJTiCdsE4yVO4BBJw763TDCLkrJ10QPmmHzwLw/edit?usp=sharing
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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. |
There was a problem hiding this comment.
Should we include a link to a previous release webinar?
There was a problem hiding this comment.
good idea. I couldn't find a playlist with all of them, so I just linked to the last few 6ceea98
dipesh-rawat
left a comment
There was a problem hiding this comment.
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. |
There was a problem hiding this comment.
This note feels a bit out of place here, or I may be missing something.
|
|
||
| #### 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. |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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
|
@dipesh-rawat: The label(s) DetailsIn response to this:
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. |
| - [Code Freeze Templates](#code-freeze-templates) | ||
| - [Code Freeze Party Templates](#code-freeze-party-templates) | ||
|
|
||
| ## SIG Outreach Templates |
There was a problem hiding this comment.
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%;"> |
There was a problem hiding this comment.
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!
dipesh-rawat
left a comment
There was a problem hiding this comment.
Thanks for making these changes. They are really useful and much needed.
/lgtm
|
Thanks for the changes Jenny. |
|
Great improvement! /lgtm |
|
[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 DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
What type of PR is this:
/kind documentation
What this PR does / why we need it:
Which issue(s) this PR fixes:
N/A
Special notes for your reviewer: