Coordinating major themes collection for a release

[wilsonehusin]

As part of a Kubernetes release, the release team compiles a list of major themes. We have multiple publish locations for this and they have varying content. For example: release blog and release notes.

In Kubernetes 1.20, we have coordinated effort of a primary file on compiling the entries to this list. This discussion is opened to find out how we can further formalize the process.

Some goals I can think about (please weigh in / add / remove):

• Consistency between published medias -- or not! I think we need justifications for either
• Structured workflow such that SIG Chairs / PR authors will reach out to us (release team) if they have entries to submit, such that:
  • SIG Chairs know that they need to submit it to release team
  • Release team know if something needs to be added (e.g. on PR for feature gate change, ask if this should go to major themes as well)
  • This will also pave the way for automation, similar to how each PR asks for release notes
• Early start on compilation so that we leave enough time for reviewers (i.e. technical writers / SIG Docs), instead of rushing everything on the last week or two

With all that being said, I'd like to invite the 1.21 enhancement, docs, & comms leads to start! (of course, everyone is welcomed 😄)

cc: @annajung @reylejano @divya-mohan0209

[justaugustus]

Please add this as part of kubernetes/community#5344.

/close