...
Table of Contents | ||
---|---|---|
|
ArchitectureDescriptiondescriptionObservationResponsibilities and delivery process unclear. Stakeholders and tasks are not covered by the release process. Updates for the architecture description must be manually inquired from the Architecture Subcommittee and LFN Marketing and hence are provided late in the release process. Relevant articles to be checked and updated arefiles: Suggestion for Improvement
| |
Marketing/CompositeRelease Noterelease noteObservationResponsibilities and delivery process unclear. Stakeholders and tasks are not covered by the release process. Who is in the lead to use the content provided in the 'Release Key Updates' to create the Marketing/Composite Release Note? Content in 'Release Key Updates' (e.g. for the 'istanbul' release) is partly not provided by the projects/subcommittees. Partly is must be rephrased to be used in the Marketing/Composite Release Note. x Suggestion for Improvement
| |
Branching of repositoriesObservationxSee Increased transparency on software modules included in an ONAP release Suggestion for Improvement | |
Management of ONAP projects/software modules participating in a releaseObservationSee Increased transparency on software modules included in an ONAP release Suggestion for Improvement | todo|
Process to create documentation not clear Process descriptionfor 'doc' project team to create ONAP documentation ObservationFor the 'doc' project team there is no clear set of instructions to create the release specific documentation for an ONAP release. Suggestion for Improvement
| |
Processto create documentation not cleardescription for ONAP project teams to create project documentationObservationFor the ONAP project teams there is no clear set of instructions to create the release specific project documentation for an ONAP release. Suggestion for Improvement
|
...