...
- A deployable ONAP release consists of 'maintained' an 'unmaintained' software modules
- Only 'projects' are managed in the release process
- But a 'project' consists of 1-n repositories. Repositories are not managed in the release process.
- Only 'maintained' projects are managed in the release process.
- But "unmaintained" software modules (docker container) are added to the list of deployed software modules in the end of the release process
- The management of 'release partizipation' is limited (projects/repositories), distributed (rel mgr, oom, sec, doc) and is not done in an end-to-end manner
- Information about the lifecycle state of projects and repositories and their release partizipation is distributed, manually maintained and not in sync (GIT:active|readonly, INFO.YAML, WIKI:release partizipation, WIKI:project lifecycle state, WIKI:documentation, ...)
Proposal
The information about software modules included in an ONAP release must be managed ...
...