DRAFT
Work in Progress
This content is currently being worked on to scope out the responsibilities and processes around release planning.
Execution / how release is done
How we determine what content we expect to put into the release
- high level terms/themes / multiple releases → Epics, deliverables
- tracking zenhub, github projects boards - transparent/clear - easily see status of a release
- communicate what is in a release. release notes are weak. build earlier in cycle / as we go along
tagging of defect fixes as go into release
delivery pipelines/release pipelines – implementation
Adoption/architecture - what does doing a release mean. docs/code - what does someone get. comms, blog posts, allowing to make use of release
Need volunteers - to have a more hands on role
- Long running themes
- Major Changes
- Bug Fixes
- Dependencies
- Build Pipelines
- Release Pipelines
- Consumption