Age | Commit message (Collapse) | Author | Files | Lines |
|
JIRA: COPPER-7
Change-Id: I209a27f6ba25183e894204c6a2fa22dd73128254
Signed-off-by: blsaws <bs3131@att.com>
|
|
JIRA: COPPER-7
Change-Id: I68fa9bdb789cb83073560e3352709a6b7fc02a6c
Signed-off-by: Bryan Sullivan <bs3131@att.com>
|
|
- doc8 violations
- use latest index.rst format
- move userguide.rst to featureusage.rst
Change-Id: I73e0a8a45418e197b973537d4f2856bd98c9a06c
Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
|
|
JIRA: COPPER-1
Change-Id: I1edfdbc55d4d3fd0c43cddba45e26eb515728cca
Signed-off-by: SULLIVAN <bs3131@att.com>
|
|
JIRA: COPPER-7
Change-Id: Ifbaf72022c0afe1e40077dbe94d316af16e74927
Signed-off-by: blsaws <bryan.sullivan@att.com>
|
|
JIRA: COPPER-7
Change-Id: I13820a26f09a5c5a002700ee22da5976f49f04e3
Signed-off-by: blsaws <bryan.sullivan@att.com>
|
|
The featureconfig.rst document should be used to describe the
configuration of the <XYZ> feature. The content will be added to the
Brahmaputra configuration guide which intends to describe how to
configure the Brahmaputra release to a stable and ready state For
feature projects this should refer to the use of deployment tool
scenario selections and post deployment configuration specific to the
feature. Also added is the postinstall.rst document for features to
describe how to check and analyze the result of test cases for
respective feature.
Change-Id: I3a2939cfcd733b1346bd9e459fbb70c855699bb8
Signed-off-by: Sofia Wallin <sofia.wallin@ericsson.com>
|