You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

NOTE: This document complements: Increased transparency on software modules included in an ONAP release

Architecture Descriptions

Observation

Responsibilities and delivery process unclear. Stakeholders and tasks are not covered by the release process. Updates for architecture descriptions 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 are:

Suggestion for Improvement

x

Marketing/Composite Release Note

Observation

Responsibilities 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

x




  • No labels