Updated Release Notes

[appc.git] / docs / release-notes.rst

diff --git a/docs/release-notes.rst b/docs/release-notes.rst
index ba42b1b..9cae7fa 100644 (file)
--- a/docs/release-notes.rst
+++ b/docs/release-notes.rst
@@ -1,4 +1,4 @@
-.. ============LICENSE_START==========================================
+.. ============LICENSE_START==========================================
 .. ===================================================================
 .. Copyright © 2017-2018 AT&T Intellectual Property. All rights reserved.
 .. ===================================================================
@@ -113,9 +113,13 @@ The following defects that were documented as known issues in Amsterdam have bee
        
 **Known Issues**
 
-The following issues remain open at the end of Beijing release. 
+The following issues remain open at the end of Beijing release. Please refer to Jira for further details and workaround, if available.
 
-       - `APPC-912 <https://jira.onap.org/browse/APPC-912>`_ - MalformedChunkCodingException in MDSALStoreImpl.getNodeName
+    - `APPC-940 <https://jira.onap.org/browse/APPC-940>`_ - APPC CDT Tool is not updating appc_southbound.properties with the URL supplied for REST
+
+    - `APPC-929 <https://jira.onap.org/browse/APPC-929>`_ - LCM API - ConfigScaleOut- Payload parameter to be manadatory - "true"
+ 
+       - `APPC-912 <https://jira.onap.org/browse/APPC-912>`_ - MalformedChunkCodingException in MDSALStoreImpl.getNodeName
        
        - `APPC-892 <https://jira.onap.org/browse/APPC-892>`_ - Cntl+4 to highlight and replace feature- Textbox is accepting space  and able to submit without giving any value
 
@@ -128,13 +132,20 @@ The following issues remain open at the end of Beijing release.
        - `APPC-154 <https://jira.onap.org/browse/APPC-154>`_ - Logging issue - Request REST API of APPC has RequestID (MDC) in Body or Payload section instead of Header.
        
        
-**Security Issues**
+**Security Notes**
+
+APPC 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 APPC open Critical security vulnerabilities and their risk assessment have been documented as part of the `project <https://wiki.onap.org/pages/viewpage.action?pageId=25438971>`_.
 
-The security issues that remain open at the end of Beijing release can be found in the attached report from Nexus IQ - :download:`appc-Build-20180518-NexusIQ Report.pdf` Copy of full Nexus IQ Report.
-         
-       
 Additionally, communication over DMaaP currently does not use secure topics in this release. This has dependency on DMaaP to enable.   
 
+
+Quick Links:
+       - `APPC project page <https://wiki.onap.org/display/DW/Application+Controller+Project>`_
+       
+       - `Passing Badge information for APPC <https://bestpractices.coreinfrastructure.org/en/projects/1579>`_
+       
+       - `Project Vulnerability Review Table for APPC <https://wiki.onap.org/pages/viewpage.action?pageId=25438971>`_
+       
 **Other**
 
 - Limitations, Constraints and other worthy notes
@@ -151,4 +162,3 @@ Additionally, communication over DMaaP currently does not use secure topics in t
 ===========
 
 End of Release Notes
-