Move Major Themes responsibility from Release Notes to Comms

[katcosgrove]

What type of PR is this:

/kind cleanup
/kind documentation

What this PR does / why we need it:

The collection of Major Themes is currently handled by Release Notes, when it is more in line with the duties of the Comms team and most prominently consumed by the Comms team. To better reflect the actual behavior of the teams, I have moved the primary responsibility for collection of Major Themes to Comms, and put Release Notes in a supporting role for this duty.

Which issue(s) this PR fixes:

None

Special notes for your reviewer:

[katcosgrove]

/hold

[katcosgrove]

/assign @a-mccarthy

Since you are the incoming Comms lead, this will affect you. Thoughts?

[a-mccarthy]

Sounds good to me. I think it makes sense to move over the responsibility to comms since we are the primary folks using this content for our release deliverables. 👍

[ramrodo]

I agree with this proposal.
Thanks, Kat for organizing this.
/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: katcosgrove, ramrodo

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• release-team/role-handbooks/communications/OWNERS [katcosgrove]
• release-team/role-handbooks/release-notes/OWNERS [katcosgrove,ramrodo]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[katcosgrove]

/unhold

Thanks y'all!

[fsmunoz]

Late to the party, but completely in agreement with the proposal, this was one of the suggestions I had for the 1.29 retro since the current situation is an artefact of how things were done in the beginning (when Release Notes were the single source of updates for a release, before there was a release blog), this suggestions greatly clarifies things and puts them in line with current practices.

/lgtm

[shopdrop1]

@