...
- Store documentation source in gerrit project project repositories in a form that is easy for multiple authors to create and maintain.
- Define and integrate source sources from multiple repository locations into an complete, organized set for an ONAP release.
- Automatically (re)create a complete set of finished documentation whenever any sources change.
- Publish the a finished set of formal change-controlled documentation in where it can be easily referenced by any user audience that is working with an the ONAP Beijing release.
- Produce intuitive, introductory documentation and testing sandbox for ONAP novices
Minimum Viable Product
Final documentation for ONAP Release 2 Beijing Use Cases
Functionalities
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
Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project=sanbox and issuetype in (epic) serverId 425b2b0a-557c-3c0c-b515-579789cceedb
Stories
| Jira | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
https://jira.onap.org/secure/RapidBoard.jspa?rapidView=37&view=planning.nodetail&epics=visible
Stories
Longer term roadmap
Indicate at a high level the longer term roadmap. This is to put things into the big perspective.
...
Provide a link toward the list of all known project bugs.Jira
Risks
List the risks identified for this release along with the plan to prevent the risk to occur (mitigation) and the plan of action in the case the risk would materialized (contingency).
...