diff options
| author |   seshukm <seshu.kumar.m@huawei.com> | 2018-06-07 11:28:08 +0800 |
|---|---|---|
| committer | seshukm <seshu.kumar.m@huawei.com> | 2018-06-07 11:28:08 +0800 |
| commit | 5620466ed7664346278e99967d8600b127454091 (patch) | |
| tree | 6ef04eaff2b059bda612460fcbdc1db670247776 | |
| parent | 296ce73c352e4c3de7d4f1ad588d9a5383caa030 (diff) | |
Update Known issues
Issue-ID: SO-660
Change-Id: Iec417a8a70c496cccf111f8a0fe3599f0d73ed23
Signed-off-by: seshukm <seshu.kumar.m@huawei.com>
| -rw-r--r-- | docs/release-notes.rst | 11 |
1 files changed, 6 insertions, 5 deletions
diff --git a/docs/release-notes.rst b/docs/release-notes.rst index ffde7ac311..b27b2a3eca 100644 --- a/docs/release-notes.rst +++ b/docs/release-notes.rst @@ -1,6 +1,6 @@ .. This work is licensed under a Creative Commons Attribution 4.0 International License. .. http://creativecommons.org/licenses/by/4.0 -.. Copyright 2017 Huawei Intellectual Property. All rights reserved. +.. Copyright 2018 Huawei Intellectual Property. All rights reserved. Service Orchestrator Release Notes @@ -27,15 +27,16 @@ The Beijing release is the second release of the Service Orchestrator (SO) proje **Bug Fixes** -The defects fixed in this release could be found `here <https://jira.onap.org/issues/?jql=project%20%3D%20SO%20AND%20affectedVersion%20%3D%20%22Beijing%20Release%22%20AND%20status%20%3D%20Closed%20>`_. + The defects fixed in this release could be found `here <https://jira.onap.org/issues/?jql=project%20%3D%20SO%20AND%20affectedVersion%20%3D%20%22Beijing%20Release%22%20AND%20status%20%3D%20Closed%20>`_. **Known Issues** -SO docker image is still on ecmop and not onap in the repository. -This will be addressed in the next release. + + SO docker image is still on ecmop and not onap in the repository. + This will be addressed in the next release. **Security Notes** -SO code has been formally scanned during build time using NexusIQ and all Critical vulnerabilities have been addressed, items that remain open have been assessed for risk and determined to be false positive. The SO open Critical security vulnerabilities and their risk assessment have been documented as part of the `project <https://wiki.onap.org/pages/viewpage.action?pageId=28377799>`_. + SO code has been formally scanned during build time using NexusIQ and all Critical vulnerabilities have been addressed, items that remain open have been assessed for risk and determined to be false positive. The SO open Critical security vulnerabilities and their risk assessment have been documented as part of the `project <https://wiki.onap.org/pages/viewpage.action?pageId=28377799>`_. Quick Links: |