X-Git-Url: https://gerrit.onap.org/r/gitweb?a=blobdiff_plain;f=docs%2Frelease-notes.rst;h=7c5b9ff58a5202323308cacf47034b84d520c88e;hb=3a2c70f1ee024dbad4dc091d3105064641908e1d;hp=8ec147978a932fde9afc7774df70513d5dd7d6ae;hpb=aa45bd087308d7881be0758a0ae4bc652e274ce6;p=holmes%2Frule-management.git

diff --git a/docs/release-notes.rst b/docs/release-notes.rst
index 8ec1479..7c5b9ff 100644
--- a/docs/release-notes.rst
+++ b/docs/release-notes.rst
@@ -14,30 +14,42 @@ ocean of events collected from different levels of the telecom cloud.
 Version: 1.0.0
 --------------
 
-
 :Release Date: 2017-11-16
 
 
-
 **New Features**
 In the Amsterdam release, Holmes is mainly intended to support the alarm
 correlation analysis for the VoLTE scenario. To get us there, Holmes provides
 the following features:
+
 - `Rule Management <https://jira.onap.org/browse/HOLMES-4>`_ The feature provides interfaces for the users to create, query, update and delete rules. In this release, they are used along with the DCAE interfaces to accomplish the deployment (creation/update) of the control loop related rules.
+
 - `Engine Management <https://jira.onap.org/browse/HOLMES-5>`_ The feature is not exposed to the end user directly. It's mainly used internally by Holmes as a container for the execution of rules. It provides interface for rule verification and deployment/un-deployment.
 
 **Bug Fixes**
 
+This is the initial release.
+
 **Known Issues**
 
+If the database is not stable, there may be data/status inconsistency between the rule management module and the engine management module.
+
 **Security Issues**
 
+N/A
+
 **Upgrade Notes**
 
+This is the inital release.
+
 **Deprecation Notes**
 
+N/A
+
 **Other**
 
+N/A
+
 ===========
 
 End of Release Notes