Clarify optional template sections
Clarify optional template section and expected depth based on input from the product working group. Refer to this thread for further background: http://lists.openstack.org/pipermail/product-wg/2015-July/000485.html Change-Id: Idf67d88ac535001d703b6337186a49b400bf2b17
This commit is contained in:
parent
186967526d
commit
88c1d86e23
13
template.rst
13
template.rst
@ -76,14 +76,17 @@ If you are aware of any work in progress that will affect this use case,
|
|||||||
please list it here. Include links to a spec or blueprint or bug report
|
please list it here. Include links to a spec or blueprint or bug report
|
||||||
where applicable.
|
where applicable.
|
||||||
|
|
||||||
|
Please note that this step is optional, leave this section blank if you are
|
||||||
|
unsure.
|
||||||
|
|
||||||
Requirements
|
Requirements
|
||||||
============
|
============
|
||||||
|
|
||||||
Use this section to define the functions that must be available or any
|
Use this section to describe the functions you need to successfully support
|
||||||
specific technical requirements that exist in order to successfully
|
your use case. If you have requirements which are currently not addressed by
|
||||||
support your use case. If there are requirements that are external
|
OpenStack please highlight them. Note however, this will not mean that they
|
||||||
to OpenStack, note them as such. Please always add a comprehensible
|
necessarily will be implemented. Please refrain from specifying implementation
|
||||||
description to ensure that people understand your need.
|
details.
|
||||||
|
|
||||||
* 1st Requirement
|
* 1st Requirement
|
||||||
* 2nd Requirement
|
* 2nd Requirement
|
||||||
|
Loading…
Reference in New Issue
Block a user