Skip to content

Branch management handbook de-duplication of content + reorg docs structure #2797

@mbianchidev

Description

@mbianchidev

Clean up the branch manager handbook - basically remove the content already present in release cut docs from it and reorganize the structure of it.

New structure proposed (thanks @wendy-ha18 for reminding me about these charts):

release-engineering/ ├── README.md # overview of the team, communication channels, responsibilities, etc. ├── handbooks/ # Shared resources for both Branch Managers (X.Y.0) and Patch Release Managers (X.Y.Z) ├── k8s-release-cut.md ├── go.md ├── post-rc0-release-task.md ├── patch-releases.md ├── cherry-picks.md ├── cve-patch.md ├── .... └── README.md # explaining everything contained in the hadnbooks and grouping them a bit based on (maybe even roles, but more situations, things to do) 

/kind documentation
/priority important-longterm

Blocked by #2796

/assign @mbianchidev

Metadata

Metadata

Assignees

Labels

kind/documentationCategorizes issue or PR as related to documentation.priority/important-longtermImportant over the long term, but may not be staffed and/or may need multiple releases to complete.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions