Docs release meister for K8s 1.11

1dot11_release_meister.md

Handing over the release meister role

Thanks for taking on the release 1.11 release meister role for K8s SIG Docs!

Things to do

1. Open a PR to update the official release team doc: https://github.com/kubernetes/sig-release/blob/master/releases/release-1.11/release_team.md.

2. Introduce yourself to the 1.11 release lead, Josh Berkus (@jberkus on Kubernetes Slack).

3. Start attending SIG Release meetings (currently weekly, Mondays 11am Pacific, cadence will accelerate as release progresses).

4. Manage the release branches.

   I recommend updating release-1.11 as soon as possible, and working with people who've already opened PRs against the branch to get them aligned with the new content tree post-Hugo migration.

   I also recommend delaying updates to release-1.10 until we've done as much work as possible to bring the Reference page back into alignment with 1.10 organization. Until we re-add all of the APIs to master, docs on release-1.10 are the only available API reference for users.

Docs to track

Top priority

• 1.11 Features OSS tracking board

• Release 1.11 docs megabranch

  Note: Some PRs are already open. Work with the feature owners to close and re-open PRs against the post-Hugo migration content tree.

Reference as needed

• 1.11 Release Meeting Agendas and Minutes

• K8s 1.11 release schedule

  Open PR to track: kubernetes/sig-release#140

• 1.11 Release team contact sheet

  Make sure to update this with your contact information.

Docs playbook

Original GDoc source (@chenopis): https://docs.google.com/document/d/1PCkAwPWadlu7beprhtQLtZzgsbO8CD7SvMVzta3fhcw/edit?ts=5963ce05&pli=1#heading=h.xh7s5vn5jum9

Current source (@bradamant3): https://github.com/kubernetes/sig-release/blob/master/release-process-documentation/documentation-guides/update-release-docs-new.md

PR in progress (@zacharysarah): https://github.com/kubernetes/sig-release/pull/139/files

Missing pieces

• Remember that docs version strategy is CURRENT+4: for 1.11, supported versions will be 1.11-1.7
• Update the version selector in every supported branch (release-1.<X>)

To update the version selector, edit the config.toml, copy-paste the newest entry, and change the numbers. It looks like you also need to change the latest key and the docsbranch key, in the WIP release branch's copy of the TOML file.

Release meister must be an approver in the OWNERS file too (in order to be able to approve PRs for merge)

Release meister needs to be added to the Github repo's admins group by another admin, to be able to force-push branches