Updated the rel notes, main changes and compatibility

Release contents were updated.

Change-Id: I31ab99b8282888bfe80da47e0b81d584e1200ceb
Signed-off-by: mrpa <miruna.paun@enea.com>

2 files changed, 7 insertions, 145 deletions

diff --git a/doc/book-enea-nfv-access-release-info/doc/about_release.xml b/doc/book-enea-nfv-access-release-info/doc/about_release.xml
index 9610aa7..ed7394c 100644
--- a/doc/book-enea-nfv-access-release-info/doc/about_release.xml
+++ b/doc/book-enea-nfv-access-release-info/doc/about_release.xml
@@ -20,19 +20,19 @@
 
     <itemizedlist>
       <listitem>
-        <para>Enea_NFV_Access_Run_Time_Platform_XeonD_2.2.2.tar.gz</para>
+        <para>Enea_NFV_Access_Run_Time_Platform_XeonD_2.2.3.tar.gz</para>
       </listitem>
 
       <listitem>
-        <para>Enea_NFV_Access_Run_Time_Platform_C3000_2.2.2.tar.gz</para>
+        <para>Enea_NFV_Access_Run_Time_Platform_C3000_2.2.3.tar.gz</para>
       </listitem>
 
       <listitem>
-        <para>ucpeManager_1.1.1_b37-CentOS.tar.gz</para>
+        <para>ucpeManager_2.2.3_b1-CentOS.tar.gz</para>
       </listitem>
 
       <listitem>
-        <para>nfvaccess2.2.2_af-th.zip (Automation and Test Harness)</para>
+        <para>nfvaccess2.2.3_af-th.zip (Automation and Test Harness)</para>
       </listitem>
 
       <listitem>
diff --git a/doc/book-enea-nfv-access-release-info/doc/main_changes.xml b/doc/book-enea-nfv-access-release-info/doc/main_changes.xml
index dfa5a96..c373d39 100644
--- a/doc/book-enea-nfv-access-release-info/doc/main_changes.xml
+++ b/doc/book-enea-nfv-access-release-info/doc/main_changes.xml
@@ -12,29 +12,7 @@
   <section id="relinfo-changes-other">
     <title>New Features</title>
 
-    <itemizedlist>
-      <listitem>
-        <para>Use of OpenJDK as the Java Engine in the uCPE Manager.</para>
-      </listitem>
-
-      <listitem>
-        <para>USB Installer Web User Interface.</para>
-      </listitem>
-
-      <listitem>
-        <para>Support of ZTP extensions through custom scripting.</para>
-      </listitem>
-
-      <listitem>
-        <para>Support for uCPE device software management from the Enea uCPE
-        Manager.</para>
-      </listitem>
-
-      <listitem>
-        <para>Support for Layer 3 networking configuration from the Enea uCPE
-        Manager.</para>
-      </listitem>
-    </itemizedlist>
+    <para>No new features were added in this release.</para>
   </section>
 
   <section id="open_source">
@@ -48,123 +26,7 @@
   <section id="relinfo-backward-compat">
     <title>Compatibility</title>
 
-    <para condition="hidden">In the development of any complex software
-    platform, there is a need to strike a balance between backwards
-    compatibility and new development. In most cases, compatibility will be
-    maintained as long as reasonably possible. Necessary compatibility breaks
-    will be done only as needed and in major releases.</para>  
-
-    <para><remark>LXCR-9773</remark>The following REST API changes have been made:</para>
-
-    <itemizedlist>
-      <listitem>
-        <para>The <literal>uploadCustomScript()</literal> method included in the 
-          <literal>CustomScripts</literal> module takes in an
-        additional argument (device module name).</para>
-      </listitem>
-
-      <listitem>
-        <para>A new <literal>-- upload() --</literal> method has been added to
-          the Device Upgrade module to allow for uploads of NFV Access software 
-          images to the uCPE Manager.</para>
-      </listitem>
-
-      <listitem>
-        <para>A new <literal>-- upload() --</literal> method has been added to
-          the <literal>VnfManager</literal> module to allow uploads of VNF 
-          images to the uCPE Manager as part of the onboarding process.</para>
-      </listitem>
-    </itemizedlist>
-
-    <para>The <literal>VcpeAgent</literal> (i.e. the NFV Access device module)
-    was redesigned:</para>
-
-    <itemizedlist>
-      <listitem>
-        <para> The <literal>system-attributes</literal> config table was split
-        into <literal>system-attributes-state</literal> (operational data) and
-        <literal>system-attributes</literal> (configuration data).</para>
-
-        <itemizedlist>
-          <listitem>
-            <para> The configuration data still contains the attributes:
-            <literal>device-name</literal>,
-            <literal>device-description</literal> and
-            <literal>initial-configuration-complete</literal>.</para>
-          </listitem>
-
-          <listitem>
-            <para>The fields <literal>device-type</literal>,
-            <literal>device-version</literal>, <literal>device-id</literal>,
-            <literal>device-latitude</literal>, and
-            <literal>device-longitude</literal> are now operational data.
-            <literal>device-ip-address</literal> has been added as oper
-            data.</para>
-          </listitem>
-
-          <listitem>
-            <para>The <literal>customer-tag</literal> in release version 2.2.1
-            was a config leaf-list, it is now a leaf called
-            <literal>device-customer-tags</literal> (comma-separated).</para>
-          </listitem>
-
-          <listitem>
-            <para>The <literal>mgmt-ip-address</literal> has been added as
-            oper data. This attribute was configured within an ovs-bridge of
-            type <literal>inband-mgmt</literal>.</para>
-          </listitem>
-        </itemizedlist>
-      </listitem>
-
-      <listitem>
-        <para>The <literal>external-interface-capabilities</literal>
-        operational table now has <literal>wan</literal> and
-        <literal>mgmt</literal> Booleans.</para>
-      </listitem>
-
-      <listitem>
-        <para>The <literal>external-interface</literal> configuration table
-        now has a choice of <literal>wan</literal>. </para>
-
-        <para>New fields for this type are <literal>mgmt-interface</literal>,
-        <literal>address-assignment</literal>, <literal>ip-address</literal>,
-        <literal>gateway</literal>, and <literal>netmask</literal> (only
-        considered if static).</para>
-      </listitem>
-
-      <listitem>
-        <para>In an <literal>ovs-bridge</literal>, for the choice of
-        <literal>inband-mgmt</literal>, the <literal>mgmt-address</literal>
-        and <literal>mgmt-port</literal> fields have been removed (there are
-        no fields left in this choice).</para>
-      </listitem>
-
-      <listitem>
-        <para>In the Host operational table, there are a couple of
-        changes:</para>
-
-        <itemizedlist>
-          <listitem>
-            <para>The <literal>name</literal> field has been removed, however,
-            there is still a <literal>host-name</literal> field.</para>
-          </listitem>
-
-          <listitem>
-            <para>A <literal>machine-type</literal> field has been
-            added.</para>
-          </listitem>
-        </itemizedlist>
-      </listitem>
-    </itemizedlist>
-    
-    <para>REST clients should see only some minor changes when upgrading from 
-      NFV Access 2.2.1 to NFV Access 2.2.2. Code that deals with the 
-      system-attributes table, in-band management OVS bridges, or the host 
-      operational data may need to be modified.</para>
-    
-    <para>The new WAN interface type needs a <literal>wan-mgmt</literal> 
-      interface configured to create the <literal>in-band mgmt</literal> bridge. 
-      This should typically happen automatically as part of initial installation
-      or upgrade and should not affect the REST clients.</para>
+    <para>This release does not contain any change impacting
+    compatibility.</para>
   </section>
 </chapter>
\ No newline at end of file