-
Notifications
You must be signed in to change notification settings - Fork 428
Open
Labels
area/release-engIssues or PRs related to the Release Engineering subprojectIssues or PRs related to the Release Engineering subprojectkind/documentationCategorizes issue or PR as related to documentation.Categorizes issue or PR as related to documentation.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.Indicates that an issue or PR should not be auto-closed due to staleness.priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Description
This issue is an umbrella issue to track the progress of refactoring the release engineering handbooks.
- Split the Branch Management handbook into multiple handbooks
- Release Management handbook
- Improve the handbook formatting and wording
- Document how alpha.1 releases should be handled (alpha.1 documentation #1229)
- Consider adding a diagram describing the release process (Add basic release engineering description #1088)
- Branch Management handbook
- Ensure the handbook is up to date
- Improve the handbook formatting and wording
- Release Management handbook
- Merge the Patch Release Team handbook with the other handbooks
- Consider moving the role-handbooks in the filesystem tree above other documents
- Document the needed IAM privileges for running tasks mentioned in the handbooks
/kind documentation
/area release-eng
/priority important-soon
/milestone v1.20
/assign
saschagrunert and hasheddan
Metadata
Metadata
Labels
area/release-engIssues or PRs related to the Release Engineering subprojectIssues or PRs related to the Release Engineering subprojectkind/documentationCategorizes issue or PR as related to documentation.Categorizes issue or PR as related to documentation.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.Indicates that an issue or PR should not be auto-closed due to staleness.priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.Must be staffed and worked on either currently, or very soon, ideally in time for the next release.