diff options
Diffstat (limited to 'docs/release/templates/releasenotes/scenario/<scenarioname>.rst')
| -rw-r--r-- | docs/release/templates/releasenotes/scenario/<scenarioname>.rst | 37 |
1 files changed, 37 insertions, 0 deletions
diff --git a/docs/release/templates/releasenotes/scenario/<scenarioname>.rst b/docs/release/templates/releasenotes/scenario/<scenarioname>.rst new file mode 100644 index 000000000..47c85ec15 --- /dev/null +++ b/docs/release/templates/releasenotes/scenario/<scenarioname>.rst @@ -0,0 +1,37 @@ +.. This work is licensed under a Creative Commons Attribution 4.0 International License. +.. http://creativecommons.org/licenses/by/4.0 +.. (c) <optionally add copywriters name> + + +============================================= +<Scenario> <Release Name> Release Notes +============================================= + + +Introduction +============ +.. In this section explain the purpose of the scenario and the types of capabilities provided + +Scenario components and composition +=================================== +.. In this section describe the unique components that make up the scenario, +.. what each component provides and why it has been included in order +.. to communicate to the user the capabilities available in this scenario. + +Scenario usage overview +======================= +.. Provide a brief overview on how to use the scenario and the features available to the +.. user. This should be an "introduction" to the userguide document, and explicitly link to it, +.. where the specifics of the features are covered including examples and API's + +Limitations, Issues and Workarounds +=================================== +.. Explain scenario limitations here, this should be at a design level rather than discussing +.. faults or bugs. If the system design only provide some expected functionality then provide +.. some insight at this point. + +References +========== + +For more information on the OPNFV Colorado release, please visit +http://www.opnfv.org/colorado
\ No newline at end of file |