...
What is this release trying to address?
- Update project-level documentation for Beijing Release requirements
- Improving the Usability of the Platform:
- Establish consistent tool chain and standards for API documentation
- Create introductory documentation and "sandbox" functionality for novices to ONAP
- Refine and harden the CI/CD tool chain and processes initially established in Amsterdam
- Migrate seed documentation currently in the wiki or gerrit that is being maintained by approved projects
- Refine / expand current documentation for VNFs, OpenStack interfaces, UIs, and LF Tool Chain
- Establish feedback mechanisms in Wiki and/or Readthedocs to improve documentation
Use Cases
The documentation created by this project must support ONAP high level Beijing use cases.
Lower level use cases specific to documentation project scope include:
...
- Publish a finished set of formal change-controlled documentation where it can be easily referenced by any user audience that is working with the ONAP Beijing release.
- Novices
- Cross-project Integration / Views Produce intuitive, introductory documentation and testing sandbox for ONAP novices
Minimum Viable Product
Final documentation for ONAP Beijing Use Cases
...
List the functionalities that this release is committing to deliver by providing a link to JIRA Epics and Stories. In the JIRA Priority field, specify the priority (either High, Medium, Low). The priority will be used in case de-scoping is required. Don't assign High priority to all functionalities.
Epics
https://jira.onap.org/secure/RapidBoard.jspa?rapidView=37&view=planning.nodetail&epics=visibleJira server ONAP JIRA columns summary,type,created,updated,due,reporter,priority maximumIssues 20 jqlQuery Project = Doc and type = EPIC and status = Open serverId 425b2b0a-557c-3c0c-b515-579789cceedb
Stories
Longer term roadmap
...