2.2.0 version docs

Author: EduJGURJC

docs/demos/qoe.md

@@ -81,4 +81,4 @@
 
 <h5 class="small-subtitle">QoE testing</h5>
 
-For **execute this TJob** just run the TJob **JUnit5 QoE Meter Docker** in the project **QoE**
+For **execute this TJob** just run the TJob **JUnit5 QoE Meter Docker** in the project **`Asserting Quality of Experience in WebRTC`** (QoE in older versions)

docs/releases/index.md

@@ -5,9 +5,29 @@
 </div>
 
 <!-- ************************* -->
-<!-- ********* 2.1.1 ********* -->
+<!-- ********* 2.2.0 ********* -->
 <!-- ************************* -->
 
+<h3 id="2.2.0" class="small-subtitle">2.2.0</h3>
+<h4 class="smaller-subtitle">19/12/2019</h4>
+
+<h5 class="smaller-subtitle">Features & Improvements</h5>
+
+- <a href="https://github.com/elastest/elastest-instrumentation-manager/blob/master/docs/user-docs.md" target="_blank">EIM</a> now allows inserting / deleting **packet loss** in the SuT without cron
+- The names of some demo projects have been changed:
+  - **EMS Example** to **Building assertions with monitoring data**
+  - **EDS Example** to **IoT device emulation**
+  - **QoE** to **Asserting Quality of Experience in WebRTC**
+- <a target="_blank" href="/docs/jenkins">ElasTest Jenkins Plugin</a> has been updated to 1.2.0 version, which allows the <a href="https://github.com/elastest/elastest-orchestration-engine" target="_blank">EOE</a> to insert packetloss/cpu burst through the EIM.
+
+<h5 class="smaller-subtitle">Bug Fixes</h5>
+
+- Problems with **`Test Engines`** in **EK** mode have been fixed
+
+  <!-- ************************* -->
+  <!-- ********* 2.1.1 ********* -->
+  <!-- ************************* -->
+
 <h3 id="2.1.1" class="small-subtitle">2.1.1</h3>
 <h4 class="smaller-subtitle">11/12/2019</h4>
 

docs/tutorials/using-ems-to-build-tests-with-dynamic-info.md

@@ -14,7 +14,7 @@ In particular, our TJob will start one download of a large file at the beginning
 
 The ElasTest infrastructure provides us with the means to extract data from the server running the test automatically. We use this feature to collect the network activity, which we will analyse in the EMS.
 
-This example is **shipped along with ElasTest** within the project **`EMS Example`**, but we are going to explain how to create it.
+This example is **shipped along with ElasTest** within the project **`Building assertions with monitoring data`** (EMS Example in older versions), but we are going to explain how to create it.
 
 <h4 class="small-subtitle">The System under Test</h4>