[ACTION - URGENT] 1.17 Release Notes DUE THIS WEEK

[Guinevere Saenger]

Hi SIG Leads, it's your Release Lead. Below is a message from Chris Carty, in charge of release notes for 1.17. Please follow the direction at your soonest convenience. Hey Everyone,

I'm on the Release Notes Team for the release. We've put together a draft of the release notes document so far, but we need your help to make sure that the work each SIG has contributed is reflected accurately. Please check out the release notes draft document ASAP and:

1. CTRL-F your SIG and edit/move notes to a more appropriate location--we just ask that you do it as a suggestion so it's easy for the release notes team to keep track of changes.

For example, if you're the SIG lead of SIG CLI, then search for "SIG CLI". This will show release notes that were contributed by your SIG as well as release notes for features that were a collaboration between your SIG and other SIGs.

2. If you know of anything that should appear in the "Known Issues" section of the Release Notes, please leave a comment with the issue and a draft of the note text on this GitHub Issue:

3. If you have some more time and want to help shape your SIG's sections of the release notes for 1.17, there are a few more things you can do as well!

• Copy-edit notes from your SIG that may contain what you know to be technical inaccuracies, grammar inconsistencies, etc.

• Remove minor and/or non-user facing release notes contributed by your SIG

• In the sections where notes are attributed to multiple SIGs (including yours), leave a comment if the note is more related to your SIG or one of the other SIGs. We can then use this to further categorize the notes!

Thank you so much for helping put together release notes for your SIG, we know you're busy and appreciate your support of the release!

Thanks!

Chris

[Jordan Liggitt]

Is there a link to the editable document we should make suggestions to? The given link is to a github markdown file.

--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-leads" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-l...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-leads/4e9e6a32-63bb-4e43-9014-644b06801831%40googlegroups.com.

[jorge alarcon]

I believe this is the doc we need https://docs.google.com/document/d/16z0UyTkAm8cAd2ALdwZRTcOZd45mJD--d0_kiZ46Fm4/edit?usp=sharing

[Guinevere Saenger]

Dear Chairs,

Urgent reminder from the Release Team to comment on the release notes draft if you have not done so already:

Hey All,

Friendly reminder to please check out the release notes draft (https://github.com/kubernetes/sig-release/blob/master/releases/release-1.17/release-notes-draft.md) document ASAP and if you have any changes to be made to let us know, comments can be made in the following google doc https://docs.google.com/document/d/16z0UyTkAm8cAd2ALdwZRTcOZd45mJD--d0_kiZ46Fm4/edit?usp=sharing .

If you know of anything that should appear in the "Known Issues" (https://github.com/kubernetes/kubernetes/issues/83683) section of the Release Notes, please leave a comment with the issue and a draft of the note text on this GitHub Issue

Thank you so much for helping put together release notes for your SIG, we know you're busy and appreciate your support of the release!

Thanks!

Chris