[1.32] Comms Subteam Lead Progress

[mbianchidev]

⚠️ The following is a work in progress and somewhat experimental, to create an issue to track my work similar to the #2603. Follows the Release Comms Handbook that details the team's responsibilities.

Onboarding (week 1-2)

• Select shadows that will be on the team
• Make sure that your shadows...
  • Open an issue against the Kubernetes org (if not already members)
  • Sign the CLA
  • Add the Kubernetes release calendar to theirs
  • Add the Slack channels
  • Schedule the shadow orientation (general)
  • Schedule the shadow orientation (specific)
  • Have their contacts into the release contact sheet
• Coordinate with release lead to make teams.yaml updates
• Update the comms team in the teams.yaml which grants access to the comms project board
  • mbianchidev added
• Add the lead and shadows as milestone maintainers in the teams.yaml.
• Setup Comms Project Board
  • Copy prior project
  • Add v1.32 to K8s Release
  • Update the filter

Tracking (week 3-7)

• Work with the enhancements lead to understand big-ticket items to be included in the release
• Start monitoring the Feature blog opt-in sheet for new entries
• With Enhancement freeze in effect, create a GitHub discussion (example v1.26) to start collecting the Release Highlights of the release (see 1.32 discussion )
  • Reach out to all SIGs asking for an explaination of the highlights and create an ad-hoc issue for you and the shadows to track such reachout (see 1.32 issue )
• Work with Enhancements and Release Note leads to determine which deliverables are most noteworthy post-Enhancements Freeze
• Work with the Release Team and decide if the release warrants a mid-cycle 'Deprecations and Removals' blog.

Deprecation & removals and opt-in (week 8)

• Start drafting he deprecation and removals or sneak-peek blog
• Assign feature blog topics as they come in to team shadows for support and tracking efforts
• Post reminders for the feature blog opt-in
• Request placeholder PRs in k/website from all feature blog authors
• Collaborate with sig-docs-blog to establish review expectations and publication strategy
• Make sig-docs-blog review the deprecation and removals blog

Feature blogs drafts (week 9)

• Publish the deprecation and removals or sneak-peek blog
• Assign remaining feature blog topics to shadows

Release blog draft & webinar (week 10)

not so crowded due to KubeCon NA

• Create the release blog draft, if not yet started on HackMD and draft PR
• Coordinate with Release Notes to ensure Release Highlights are checked in before Code Freeze.

Before the storm (week 11)

most stuff moved here due to KubeCon NA

• Update release blog draft, post-Code Freeze, add shadows to it for help
• Ensure that short one-to-two paragraph summaries of each Release Highlights are available for the release blog from Release Notes lead or SIG Chairs
• Schedule the release Live Webinar with CNCF by emailing [email protected]. You may be referred to Calendly. The webinar is typically scheduled for 3-4 weeks after the release.
• Schedule press and analyst pre-briefings and interviews for the release lead with CNCF by emailing [email protected]
• Schedule release blog and press embargo with the CNCF
• Host a meeting with the Release Lead, Enhancements Lead, and Release Notes to discuss the Release Highlights (attached to standard RT meeting)
• Establish feature blog post-release publication schedule, typically 2-3 posts per week, at least starting a day after the release blog.
• Post the feature blog publication schedule in #sig-docs-blog
• Establish a regular cadence status check-in with the #sig-docs-blog team and maintain the publication schedule post in Slack to keep everyone synced
• Check status on all feature blog PRs. Keep #sig-docs-blog up-to-date for editorial review, and establish tech reviewers are available from the various SIGs
• Choose the next Comms Lead

The actual storm (week 12-13)

• Feature blog reviews starts (week 12)
• Check status with Release Notes lead on content for the Known Issues section of the release blog
• Continue to partner with #sig-docs-blog for editorial review, work with shadows to ensure tech reviews are moving forward from SIGs
• Connect with Release Lead to ensure theme and release logo will be ready for release blog (not required for draft)
• Finalize Release blog final draft and start review cycle, ensure it's ready for Docs Lead to publish on release day
• Send release blog draft to CNCF (week 13)
• Ensure first few feature blogs are ready to publish and that review and merge plans are in place for any still outstanding. (week 13)

Release and beyond (week 14+)

• Make sure the release blog is published with the final touches (logo and release name)
• Continue to facilitate publication of remaining feature blogs, until all PRs are merged with the right publication date
• Participate in release retro
• Organize the slides for the CNCF release webinar, and send to the CNCF for review at least one week ahead of the scheduled date. (see example slides here)
• Update the Comms handbook with what you've learnt as leader (example PR: here)
• Rest!

[mbianchidev]

/assign

[mbianchidev]

/priority important-soon

[mbianchidev]

/kind documentation