...
| Name | Description | Owned by | Prerequisites | Notes |
|---|---|---|---|---|
| Name and version the release | Release naming scheme | Heather has recommended a unified release name. | ||
| Specification review | Need a process for reviewing and providing feedback to RM an RA specifications prior to publication. | Specification review process | ||
Code archive and configuration managementArchive, | Code archive SCM | |||
| Issue tracking | Need to be able to document and track requirements, bugs, tasks, etc. | Bug tracking system | OPNFV previously used Jira jira.anuket.io | |
| Project release plan | Plan submitted by each participating project that describes what the project plans to accomplish, how the work will be tested, what documentation will be produced, and what artifacts will be released. | Release Plan template | Should we use the same template that was used for OPNFV Iruya? | |
| Requirements planning | We need to agree as a project on which RM and RA requirements we will implement for a release. In addition, there may be other requirements, such as the Python 3 migration, that we may want to accomplish for a release. | Requirements planning process | For OPNFV Iruya, we had the idea of a requirements working group, which was a combination of TSC members and PTLs. | |
| Dependency planning | We need to agree as a project on which versions of major upstream dependencies (e.g., Functest, Openstack, Kubernetes, etc.) we will use | Dependency planning process | ||
| Project documentation | Individual projects have installation, programming, and user documentation. | Documentation plan | This documentation currently exists in OPNFV repos. How will we bring it into Anuket? Will we release unified documentation? | |
| RI & RC documentation | Documentation plan | |||
| RC validation | RC conformance to each RA must be validated | RC validation plan | ||
| RI validation | RI conformance to each RA must be validated | RI validation plan | ||
| Self Release | Projects that do not contribute directly to RC/RI will self-release. | Self-release process | ||
| Release artifact hosting | How will release artifacts be made available for distribution? | Release artifact hosting plan | OPNFV artifacts were available from a download page. Do we want to do this, or something else? |
Proposal on 16 Feb 2021 (Walter.kozlowski ):
- Cycle: six monthly common Anuket release cycle (all streams and projects)
- Dates: 15 June, 15 December each year
- Names: River names starting from letter "K" for the first release (15 June 2021)
- Traceability: specification, requirement and implementation traceability maintained, where required
- Full alignment between streams and projects: not mandated to allow fast pace of progress and innovation
- Detailed calendar for each release (milestones): TSC to announce in the first two weeks of the new cycle
- Repos: projects use current repos until a convergence plan is defined and executed
- Trevor Bramwell says feasible
- Documentation: streams and projects use current tools and formats, one readidocs edition for the whole release
- ....