feat(release_notes): add new features and technology updates

md/release_notes.md

@@ -2,28 +2,47 @@
 
 ## Breaking changes
 
-* For security reasons, pushing AWS user credentials to EC2 instances (as done with BCD 1.0.x) for cluster autodiscovery is no longer supported and it's replaced by an [IAM role](aws_prerequisites.md) assignement on EC2 instances. See `ec2_discovery_iam_role` into [scenarios documentation](scenarios.md).
-* `bonita_http_api` value is now set to `false` by default.
-* For a better comprehension the value of bcd_provider `on-premises` has been replaced by `static_inventory`, you may have to update your [scenarios](scenarios.md) accordingly.
-* Bonita Docker images have been moved from `roles/bonita/files/docker/` to `dependencies` directories
+The following changes introduce incompatibility with BCD 1.0:
+
+* For security reasons, pushing AWS user credentials to EC2 instances (as done with BCD 1.0) for cluster autodiscovery is no longer supported. It is replaced by an [IAM role](aws_prerequisites.md) assignment on EC2 instances. See `ec2_discovery_iam_role` in the [Scenarios documentation](scenarios.md).
+* `bonita_http_api` variable is now set to `false` by default.
+* For a better understanding, the `on-premises` value for `bcd_provider` variable has been replaced with `static_inventory`. You may have to update your [BCD scenarios](scenarios.md) accordingly.
+* Bonita Docker images have been moved from `roles/bonita/files/docker` directory to `dependencies` directory.
+* BCD commands for Provisioning are invoked with `bcd stack` parent command.
 
 ## Limitations and known issues
 
 * The same BCD stack cannot be managed with multiple BCD controller instances due to the use of Terraform "local" backend.
-* Due to [ansible issue #35255](https://github.com/ansible/ansible/issues/35255) the warning message "could not match supplied host pattern" is displayed when there is no load balancer required for a noncluster deployment:
+* Due to [Ansible issue #35255](https://github.com/ansible/ansible/issues/35255) the warning message "could not match supplied host pattern" is displayed when there is no load balancer required for a noncluster deployment:
 ```
 [WARNING]: Could not match supplied host pattern, ignoring: load_balancer
 ```
 
+
 ## What's new in 2.0.0 (2018-06-07)
 
-* This version is compatible with Bonita 7.7.0
+:fa-info-circle: This version is compatible with Bonita 7.7.0.
+
+### New features
+
+* BCD commands for [Living Application Management](_manage_living_application) (`bcd livingapp`)
+* BCD command to show BCD environment version (`bcd version`)
+* [Jenkins standalone example](jenkins_example.md) with sample BCD pipeline
+* Scenario [encryption capability](how_to_use_bcd_with_data_encrypted.md)
 
 ### Enhancements
 
-* Handle REST_API_DYN_AUTH_CHECKS environment variable of Bonita docker image
-* Deactivate by default the Bonita [HTTP API](https://documentation.bonitasoft.com/bonita/${bonitaDocVersion}/rest-api-authorization#toc9)
-* Add Google G Suite SSO support
+* Handle `REST_API_DYN_AUTH_CHECKS` environment variable of Bonita Docker image
+* Deactivate by default [Bonita HTTP API](https://documentation.bonitasoft.com/bonita/${bonitaDocVersion}/rest-api-authorization#toc9)
+* Add [Google G Suite Single Sign-On](aws_sso.md) (SSO) support
+* Ports published by the Bonita stack are configurable
+
+### Technology updates
+
+* Upgrade BCD controller with Terraform v0.11.3
+* Upgrade BCD controller with Ansible 2.5.0
+* Support Provisioning of Ubuntu 16.04 hosts (in addition to Ubuntu 14.04)
 
 ### Bugfixes
-* BCD-199	bcd undeploy command fails when docker is not yet installed on target hosts
+
+* Stack undeploy command fails when Docker is not yet installed on target hosts