This document covers the responsibilities, time commitments, and timeline for Docs Leads shepherding docs releases for Kubernetes. Docs Lead Shadows should also read through this document and understand the launch processes so they can do it in the future.
Please refer to the Docs Release Timeline for an exhaustive list of the responsibilities of the Docs Lead.
| Variable | Explanation | Example |
|---|---|---|
| [current release] | Active Kubernetes release | 1.27 |
| [future release] | Release that the team is actively composing | 1.28 |
| [integration branch] | A PR [WIP] merging dev branch into main | Official 1.27 Release Docs dev branch |
The Docs Lead is responsible for working with the Release Team to coordinate documentation updates for the next Kubernetes release.
Responsibilities include:
- Identifying new Kubernetes features and enhancements (Kubernetes Enhancement Proposals, also referred to as KEPs) that require new documentation and tracking them using the Enhancements Tracking sheet created for the release (e.g. Example Enhancements Tracking sheet from the Kubernetes 1.26 Release)
- Creating a dev branch used by contributors to target documentation updates for the upcoming release
- Offering guidance to contributors about how to contribute new feature and enhancements documentation and working with contributors to modify existing docs to accurately represent any upcoming changes
- Providing weekly updates to the Release Team about the current state of release-bound docs
- Mentoring Docs Lead Shadows throughout this process and empowering them with the knowledge needed to be future Docs Leads
- Working with SIG-Docs to review documentation PRs according to the website Style Guide to ensure quality
- Working with SIG owners to ensure documentation is reviewed for technical accuracy
- Working with Release Comms to review the Release Blog
- Approving reviewed documentation to ensure its inclusion in the upcoming release
- Migrating the old website [version] documentation and updating it with the new release
- Communicating changes with all of the localization branches in order to stay synced across repositories
- Updating the Docs Lead and Shadow Handbook and Release Team Onboarding Guide instructions following each release
Before continuing on to the Docs specific requirements listed below, please review the tasks in the Release Team Onboarding Guide.
Releases are usually 15 weeks long. In general, there is less work in the first few weeks of the release cycle, more work in the middle as KEP owners need to be reminded to contribute documentation updates, and a lot of work in the last few weeks of the release cycle as documentation must be reviewed and approved prior to release day. The largest time commitment for the Docs Lead is the release day itself, because on that day the Docs Lead must follow the process to merge all documentation updates and unfreeze the website.
General time requirements for leads and shadows are:
- ½ hour to 2 hours a day, reviewing incoming enhancements, tracking documentation PRs, and monitoring Slack
- Between 1 and 2 hours a week to attend the majority of Release Team (weekly) and Burndown meetings (daily during Code Freeze), subject to time zone appropriateness
- Up to 1 hour weekly to attend SIG Docs meetings for status reports
During the last weeks of the release, shadows should expect to spend at least 5 hours and leads at least 10 hours finalizing the launch.
In addition to the time requirements above, a Docs Lead must:
- Familiarity with Github
- Have the ability to add a milestone to issues, so must be a member of the website milestone maintainers. Access can be requested by creating a PR against
kubernetes/orgrepo.
Note: access to see website milestone maintainers is restricted to Kubernetes GitHub org members
- Have the ability to
/approvePRs. Access can be requested by creating a PR againstmainbranch. - Take the Inclusive Speaker Orientation (LFC101) training course
Docs Lead Shadows are people who are preparing to be a Docs Lead in the future. In addition to the time requirements above, shadows must:
- Have signed the contributor CLA for Kubernetes.
- Be invested in becoming an org member within the release cycle. This can often be achieved during the release cycle with sponsorship from a role lead. See the Release Team onboarding guide for more details.
- General knowledge of our SIG-Docs areas of responsibility.
- Experience with the general process involved with contributing to Kubernetes website.
- Be a milestone maintainer in order to have the ability to add a milestone to an issue. Access can be requested by creating a PR against
kubernetes/orgrepo.
Reference the Docs Release Timeline for key dates and responsibilities during the release cycle and the Kubernetes Release Information page for the specific release (e.g. Kubernetes 1.28 Release Information page for information regarding the current release cycle including important dates, Release Team contact information, tracking spreadsheets, and more.