search
attachments
weblink
advanced
Overview
Content Tools
- Anuket resources are very thin so hard to get anyone to work on the project
- Review of the project within Anuket – Some do not need release managers (Thoth), Some are not active, Some need releases (Functest, VinePerf, CIRV, Kuberef) and finally the reference docs.
- TSC could serve as a release manager with a stronger community
- We should support projects which do not follow the Anuket release model
- There are different categories of the projects
- Projects that do not need releases (Thoth)
- Inactive projects should just be archived
- Reference docs – need minimal release support (set dates and gather requirements)
- Set the dates for the release - TSC
- Release plan - sub-project teams/PTL
- Release tags in Jira and GitHub - TSC
- Associate Issues with the GitHub project plan - PTL
- Proofreading - PTL
- Release branch creation - TSC
- Readthedocs branch creation - TSC
- Sub-project release highlights - PTL
- Blogpost, release announcement - TSC
- Test projects
- Set the dates for the release - TSC
- Release plan - sub-project teams/PTL
- Release tags in Jira and GitHub - TSC
- Associate Issues with the GitHub project plan - PTL
- Documentation done - PTL/Team
- Keep two releases per year
- Update the release framework tasks with the slimmed down version
- Next steps:
- Gergely Csatari Propose a new release process template based on this: Orinoco Release Progress