Skip to content

[v1.33] Release Comms Subteam Cycle Progress #2718

New issue
New issue
Open
Open
[v1.33] Release Comms Subteam Cycle Progress#2718
Assignees
rytswd
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.
@rytswd

Description

@rytswd
rytswd
opened on Feb 4, 2025

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.33/README.md.

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

Overview

Latest Update

As of Thursday, 24th April (week 15)

  • The release went out, and so did the release announcement blog!
  • The Feature Blogs are still being worked out

As of Saturday, 19th April (week 14)

  • Release Announcement blog write-up is mostly complete, we need final review and approval (we have received some approvals already)
  • Feature Blogs are still being tracked, and 2 are merged, and 16 are still under review (12 have received some LGTM, though)

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: Onboarding

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

  • Onboard the shadows
    • Select the shadows
    • Prepare the onboarding presentation
    • Run down Comms expectation in a meeting
    • Provide all the relevant information for the action items for the shadows
    • Update contact details for the shadows in the release contact sheet
  • Update the k/org's /config/kubernetes/sig-release/teams.yaml
    • This gives access to the Comms Project Board (Link to be fixed)
    • We need the lead and shadows to be listed as milestone maintainers
    • Add the lead
    • Add the shadows
  • Setup Comms Project Board
    • Copy prior project
    • Adjust the filter setup so that we can track both Feature Blogs as well as overall enhancements

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

  • There is a delay in the actions above due to unexpected circumstances for @rytswd
    • The delay can be up to week 4, and will be tracked more closely on the timing and prioritisation

Week 3, 4, 5, 6, 7: Tracking

The main tracking starts as the enhancement freeze comes into play. For v1.33, the enhancement freeze takes place on week 5.

For Lead

  • Work with the Enhancements lead to understand big-ticket items to be included in the release
  • Work with Enhancements and Docs leads to determine which deliverables are most noteworthy post-Enhancements Freeze
  • Prepare the Comms board with Feature Blog opt-in reach-out assignees
  • With Enhancement freeze in effect (in week 5), prepare for Release Highlights
  • Work with the Release Team and decide if the release warrants a mid-cycle 'Deprecations and Removals' blog.

For Lead and Shadows

  • 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

  • For v1.33 we are tracking this with the following board: 1.33 Enhancements Tracking (view)
  • With the enhancement freeze in place, we discussed the potential need for mid-cycle blog in the Release Lead sync meeting
  • It is likely we will need the deprecation notice, especially for Deprecate v1.Endpoints enhancements#4974
  • The opt-in reach-out was slightly delayed than usual, but still on track to complete in time
  • [Additional notes from 22nd March] There was no proper coordination with Enhancements and Docs team during these weeks, as the schedule didn't quite work out for the leads. This was probably not a deal breaker, but would have made it easier to write the sneak peek blog if we had more clear ideas.

Week 8: Feature Blog Deadline + Mid Cycle Blog

For v1.33, the Feature Blog freeze takes place on week 8. Also, the Mid Cycle Sneak Peek blog is set to be published on week 11, and thus we would need to start the sneak peek blog draft early enough. The week 8 is a good target to keep in mind.

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

Status Summary / Note for Reference

  • The draft has been created using Google Doc (access given only to Comms team)
    • This was made only on early week 9 -- I should have created this earlier, but I had to also prepare some materials to guide the team about what actions we need to take

Week 9: Focus on Mid Cycle Blog

As the mid cycle blog needs to be reviewed by the SIG Docs Blog team, the target is to get the blog ready for review this week, getting ready for the publish target of early week 11 for v1.33.

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

  • Mid cycle blog PR opened on Saturday, a bit late but thanks to reviewers, this is in line with the original timeline
  • Mid cycle blog template needs further adjustments fixing some wrong links, titles, etc.

Week 10: Release Blog Draft & Mid Way Retro

For v1.33, the code freeze takes place this week. The deadline of Release Highlights is week after (week 11), and thus we start preparing for the Release Announcements write-up

For Lead

  • Start drafting the Release Announcement blog
    • The initial draft can happen outside PR
    • Previous Release Announcements: v1.29, v1.30, v1.31, v1.32

For Lead and Shadows

A bit of slow time other than the mid cycle blog to be finalised.

  • Join retrospective for sharing anything you learned from the cycle so far

Status Summary / Note for Reference

  • The draft has been created using Google Doc
  • The PR will be created at a later date

Caution

Items below are copied over from the previous release, and needs to be updated to map correctly with 1.33 release.

  • Coordinate with Release Notes to ensure Release Highlights are checked in before Code Freeze.

Week 11: Mid Cycle Blog Published + Start of Burndown Meetings

The mid cycle blog goes out, and Release Highlight deadline is on this week. With the code freeze done in the previous week, we should be ready for getting more contents in place for the Release Announcement. However, for this release, we need to note how KubeCon takes place in the week after, and some of the schedule may need to be tweaked due to that.

For Lead

There are many items in week, and anything that couldn't get completed should be carried over in the week after (which is during KubeCon).

  • Publish the mid cycle sneak peek blog (24th March, 2025)
  • Make sure Release Highlights details are shared in the discussion ticket
    • This is to ensure transparency for all the Release teams
  • Review Feature Blog assignment following the code freeze, and re-assign as necessary
  • Run down the Release Announcement details for the team
  • 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
  • Discuss the Release Highlights status with the Release Lead, Enhancements Lead, and Docs Lead (during the RT meeting)
  • Establish Feature Blog publication schedule, typically 2-3 posts per week, at least starting a day after the release 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
  • Choose the next Comms Lead

For Lead and Shadows

  • Send final reminder about the Release Highlights (the deadline is on Tuesday, 25th March, 2025)
  • Join burndown meetings
    • As of writing (22nd March), the burndown meeting is likely to take place asynchronously on Slack
    • Lead or shadows will be asked to provide the RAG (Red Amber Green) status
  • Send a reminder to Feature Blog authors (deadline on week 13)
    • Once the write-up is ready for review, we need to ensure we have the right parties engaged in the review (sig-docs-blog, associated SIGs, etc.).
  • Prepare Feature Blog publication schedule internally
    • Once finalised, the schedule needs to be shared in #sig-docs-blog
  • Start writing up Release Announcement blog draft
    • Each member should have a handful of sections to work on
    • Ensure each of the Release Highlights gets a one-to-two paragraph summary, following updates from SIGs

Status Summary / Note for Reference

  • The mid cycle blog is set to be published on Monday morning as we got all the approvals in place beforehand.

Week 12: KubeCon EU

Because of KubeCon taking place, this week would be light in terms of the actions. However, as the many of the actions have started from week 11, any work should continue in this week, especially around the Release Announcement write-up which takes quite some time.

Also, if you are attending KubeCon, join the maintainer summit to meet the team!

Week 13: Crunch time

For v1.33, Feature Blog reviews start taking place from week 13.

For Lead

  • Check status with Docs 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 Announcement blog draft and start review cycle, ensure it's ready for Docs Lead to publish on release day
  • Share the Release Announcement blog PR in #chairs-and-techleads channel to get technical reviews
  • 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.

For Lead and Shadows

  • TBC

Status Summary / Note for Reference

  • TBC

Week 14: Getting Ready for Release

As the release coming up so near, we should be done with most of the actions by the end of week 14.

For Lead

  • Ensure the Release Announcement blog PR main write-up is merged
  • Continue to facilitate publication of remaining feature blogs, until all PRs are merged with the right publication date

For Lead and Shadows

  • TBC

Status Summary / Note for Reference

  • TBC

Week15: Release + Post Release Actions

For v1.33, the release is planned on Wednesday 23rd April 2025. At this point, there shouldn't be too much that we need to handle other than last minute juggling...

For Lead

  • Update the Release Announcement blog with the logo and release name!
  • Continue to facilitate publication of remaining Feature Blogs, until all PRs are merged with the right publication date
  • Update the Comms handbook with what you've learnt as leader (example PR: here)
  • 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)
  • Close all the outstanding tickets
    • This ticket for tracking Comms progress
    • Release Highlight discussion
    • Post-release handbook / template update PRs
    • ... and any other tickets that was created

For Lead and Shadows

  • Participate in release retro

Status Summary / Note for Reference

  • TBC

Other Follow-up Actions and Notes

  • We should make clarification on when the Feature Blog opt-in reach-outs to happen (it was a bit vague)
  • In the opt-in reach-out, we should consider whether Feature Blog write-up was done in the past
  • We should remove the duplicated Project Board view, and adjust the column and field wording
  • Make sure all the templates use the consistent KEP referencing of something like: [KEP-4974: Deprecate v1.Endpoints](https://kep.k8s.io/4974)
  • Document the version should be "v" prefixed
  • Update the blog status field to prefix with some numbers (the current "ready for review", "review in progress", "ready to publish" are all so similar and hard to see which one's which...)
  • When getting the placeholder blog PRs for Feature Blogs, we will need to get the KEP authors to come back to us in the KEP. There were a few blogs I only caught by going through the list of blog PRs, and it was quite manual.

Old Updates

As of 11th March (week 9):

  • Concern raised around the timeline for the mid cycle blog review
  • We are keeping the current target date as is, as we should be able to land as originally scheduled

As of 10th March (week 9):

  • Updated the note here to include a heading near the top to give a quick overview, and easy access to the important links
  • The Mid Cycle Blog is being tracked under Google Doc

As of 22nd March (week 10)

  • Mid cycle blog is now finalised and set to be published on Monday at 10.30 AM UTC
  • Release Announcement draft write-up has started in an internal doc for Comms

As of 19th March (week 10)

  • Mid cycle blog is on track for the release schedule
  • Release Announcement draft write-up to start soon

As of 28th March (week 11)

  • Mid cycle blog is now published
  • All update received for Release Highlights
  • Release Announcement draft write-up has started internally for Comms

As of 2nd April (week 12)

  • Release Highlights had one KEP-4827 which was something we are not tracking in this release; there is a discussion thread to handle this
  • Release Announcement is still in-progress
  • We are currently tracking 17 Feature Blogs, and 5 are already ready for review; we will be sending reminders about the deadline coming up next week

As of Friday, 11th April (week 13)

  • 15 Feature Blogs are ready for review, and 1 more ate addition expected
  • Release Announcement blog is finally ready for review

As of Tuesday, 8th April (week 13)

  • 14 Feature Blogs are ready for review, with 2 being slightly later than the deadline. There is one more possible addition. The review has been requested to SIG Docs Blog team.
  • Release Highlights all clear, the full details in this discussion thread
  • Release Announcement is still in-progress, we are aiming to complete the initial write-up by the EOD Wednesday

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