aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorSeshu-Kumar-M <seshu.kumar.m@huawei.com>2018-01-18 07:43:00 +0530
committerSeshu-Kumar-M <seshu.kumar.m@huawei.com>2018-01-18 07:43:00 +0530
commit8bc7d66365b1422de116316bd8247b04005c47dd (patch)
tree804fe15531672d0d43f35512ff8b272369e03880
parentf48987d400a14a5eb618079cc116fa10eb9bc515 (diff)
Updated release notesamsterdam
Issue-ID: SO-378 Change-Id: I15ba390eaa40683fd6949ce10994ebded5e30eac Signed-off-by: Seshu-Kumar-M <seshu.kumar.m@huawei.com>
-rw-r--r--docs/release-notes.rst40
1 files changed, 17 insertions, 23 deletions
diff --git a/docs/release-notes.rst b/docs/release-notes.rst
index c242a3be05..6a0bde6108 100644
--- a/docs/release-notes.rst
+++ b/docs/release-notes.rst
@@ -13,21 +13,9 @@ Version: 1.1.2
:Release Date: 2018-01-18
-
-**New Features**
-
-The SO provides the highest level of service orchestration in the ONAP architecture.
-It executes end-to-end service activities by processing workflows and business logic and coordinating other ONAP and external component activities.
-
-The orchestration engine is a reusable service. Any component of the architecture can execute SO orchestration capabilities.
-
-* Orchestration services will process workflows based on defined models and recipe.
-* The service model maintains consistency and reusability across all orchestration activities and ensures consistent methods, structure and version of the workflow execution environment.
-* Orchestration processes interact with other platform components or external systems via standard and well-defined APIs.
-
-
Bug Fixes
---------
+The key defects fixed in this release :
- `SO-344 <https://jira.onap.org/browse/SO-344>`_
Only pass one VNF to DoCreateVnfAndModules.
@@ -41,18 +29,24 @@ Bug Fixes
- `SO-354 <https://jira.onap.org/browse/SO-354>`_
Change the Service Type And Service Role
-
-Known Issues
-------------
-None
-Security Issues
----------------
-None
+Version: 1.1.1
+--------------
+
+:Release Date: 2017-11-16
+
+
+**New Features**
+
+The SO provides the highest level of service orchestration in the ONAP architecture.
+It executes end-to-end service activities by processing workflows and business logic and coordinating other ONAP and external component activities.
+
+The orchestration engine is a reusable service. Any component of the architecture can execute SO orchestration capabilities.
+
+* Orchestration services will process workflows based on defined models and recipe.
+* The service model maintains consistency and reusability across all orchestration activities and ensures consistent methods, structure and version of the workflow execution environment.
+* Orchestration processes interact with other platform components or external systems via standard and well-defined APIs.
-Upgrade Notes
--------------
-None
**Deprecation Notes**