Istanbul Documentation: Lessons Learned

Architecture Description

Observation

Responsibilities 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 are:

• ONAP Overview [GIT] [RTD]
• ONAP Architecture [GIT] [RTD]

Suggestion for Improvement

• todo

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

• todo

Branching

Observation

x

Suggestion for Improvement

• todo

Process to create documentation not clear for 'doc' project team

Observation

For the 'doc' project team there is no clear set of instructions to create the release specific documentation for an ONAP release.

Suggestion for Improvement

• 'doc' team to describe the process from a 'doc' project point of view and to provide this set of instructions in the ONAP Dev Wiki. See P01: Create documentation for an ONAP release (doc project team)

Process to create documentation not clear for ONAP project teams

Observation

For 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

• 'doc' team to describe the process from a ONAP project point of view and to provide this set of instructions in the ONAP Dev Wiki. See P02: Create documentation for an ONAP release (ONAP project teams)