Skip to content

[1.35] Release Comms Subteam Cycle Progress #2877

@graz-dev

Description

@graz-dev

Note

This ticket follows the Release Team Lead Cycle Progress ticket, and is curated for Comms specific actions and plans. More of release information can be found in /releases/release-1.35/README.md.

This ticket is based on the previous issue used in v1.34, and it is planned to be updated along during the whole release cycle.

Overview

Comms Team Plan and Deadlines

Note

This plan may be subject to change over time.
You can find the plan in the v1.35 Release Comms Calendar too

  • Release Enhancements Freeze (week 5 - 16/10/2025)
  • Release Feature Blog First opt-in reach out
    • start: week 6 - 20/10/2025
    • ends: week 6 - 24/10/2025
  • Release Feature Second opt-in reach out
    • start: week 6 - 27/10/2025
    • end: week 7 - 29/10/2025 (two days before feature blog freeze)
  • Feature Blog Freeze (week 7 - 31/10/2025)
  • [OPTIONAL] Release Mid-Cycle Blog content scouting
    • start: week 7 - 27/10/2025
    • end: week 7 - 31/10/2025
  • Release Highlights opening discussion and outreach
    • start: week 8 - 02/11/2025 (a day before the deadline)
    • end: week 8 - 06/11/2025
  • Release Highlight planning issue (week 8 - 06/11/2025)
  • [OPTIONAL] Mid-Cycle Blog draft (week 8 - 03/11/2025)
  • [OPTIONAL] Mid-Cycle Blog confirmation deadline (week 8 - 07/11/2025)
  • Release Highlights Deadline (week 8 - 07/11/2025)
  • Release Feature Blog ready for review reminder
    • start: week 9 - 12/11/2025
    • end: week 10 - 19/11/2025 (two days before feature blog ready for review deadline)
  • Release Highlights second out reach / reminder
    • start: week 10 - 17/11/2025
    • end: week 10 - 20/11/2025 (8 days before the release highlights deadline)
  • [OPTIONAL] Mid-Cycle Blog Ready for Review (week 10 - 19/11/2025)
  • Release Feature Blog ready for review deadline (week 10 - 21/11/2025)
  • Release Feature Blog publication calendar ready (week 11 - 26/11/2025)
  • Release Feature Blog Start Review (week 11 - 26/11/2025)
  • [OPTIONAL] Mid-Cycle Blog Published (week 11 - 26/11/2025)
  • Release Highlights Completion Deadline (week 11 - 28/11/2025)
  • Release Announcement draft (week 12 - 01/12/2025)
  • Release Feature Blog Start Scheduling (week 13 - 09/12/2025)
  • Release Announcement Ready for review (week 13 - 10/12/2025)
  • Release announcement published (week 14 - 17/12/2025)

Latest Update

As of Wednesday, 07th October (week 4)

  • Shadows were added to the appropriate mailing lists.
  • Shadow on-boarding is completed.
  • Comms team deadline and plan is confirmed by Lead and Lead Shadows.

Currently Tracked Goals

  • Feature Blogs
    • Opt-in Outreach
  • Mid Cycle Sneak Peek Blog
    • Internal write-up
    • Official PR
  • Release Announcements
    • Release Highlights
    • Internal write-up
    • Official PR
  • Webinar and Press
    • Schedule with CNCF
    • Coordinate interview setup with press
    • Hold webinar

Useful Links

Schedule and Details

Week 1, 2, 3: Onboarding and planning

Comms work tend to focus more towards the latter half of the release schedule, and thus this is the time to prepare for the team setup.

For Lead

For Shadows

Tip

Although many actions need to be handled by the shadows themselves, it is important for the lead to guide to the right information and material for proceeding with them.

Status Summary / Note for Reference

Week 4, 5, 6, 7: Tracking

Tracking starts as the enhancement freeze comes into play. For v1.54, the Enhancements Freeze takes place on week 5 (16/10/2025).

For Lead

  • Have a clear picture of what to expect with Release Lead and other Subteam Leads
    • List all major changes to be included in this release with the Release Lead and Enhancements Lead
    • List most noteworthy deliverables post-Enhancements freeze with Enhancements and Docs Leads
  • Work with the Release Team and decide if the release warrants a Mid Cycle Blog
  • Prepare for Feature Blog opt-in reach-out
    • Send shadows instructions on how to reach out to KEP authors for Feature Blog opt-in
    • Prepare the Comms board with Feature Blog opt-in reach-out assignees
  • With Enhancement freeze in effect (in week 5 16/10/2025), prepare for Release Highlights

For Lead and Shadow

  • Start reaching out for Feature Blog opt-in for each KEP
    • Complete the first round of reach-out
    • Complete the second round of reach-out
  • Reach out to all SIGs for their input on Release Highlights
    • The deadline would be much later, and we should mark the initial reach-out

Status Summary / Note for Reference

Week 8: Feature Blog opt-in Deadline + Mid Cycle Blog

For Lead

  • Start drafting the mid-cycle sneak peek blog

For Lead and Shadows

  • Update and finalise the Feature Blog status in the Project Board
  • Pair Feature Blog authors together following SIG Docs’ writing buddy process
  • Work on the mid-cycle sneak peek blog draft

Status Summary / Note for Reference

Week 9: Focus on Mid Cycle Blog

For Lead

  • Create the mid cycle sneak peek blog PR
  • Collaborate with sig-docs-blog to establish review expectations and publication strategy
  • Notify sig-docs-blog about the review of the mid cycle sneak peek blog
  • Assign Feature Blogs to each member and clarify in the "Comms Editor" column

For Lead and Shadows

  •  Send another reminder to SIGs about Release Highlights

Status Summary / Note for Reference

Week 10: Mid Cycle Blog Review, Release Blog Draft & Mid Way Retro

For Lead

  • Start drafting the Release Announcement blog

For Lead and Shadows

  • Address review comments on the mid cycle sneak peek blog
  • Send final reminder about the Release Highlights
  • Join retrospective for sharing anything you learned from the cycle so far

Status Summary / Note for Reference

Old Updates

As of Wednesday, 24th September (week 2)

Caution

This progress issue is incomplete

Metadata

Metadata

Assignees

Labels

area/release-engIssues or PRs related to the Release Engineering subprojectarea/release-teamIssues or PRs related to the release-team subprojectneeds-kindIndicates a PR lacks a `kind/foo` label and requires one.needs-prioritysig/releaseCategorizes an issue or PR as relevant to SIG Release.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions