diff --git a/docs/configuration.rst b/docs/configuration.rst
index fcd339b..306cb50 100644
--- a/docs/configuration.rst
+++ b/docs/configuration.rst
@@ -255,6 +255,8 @@ About SSL certificate validation
 
 SSL usage is enforced, this means you cannot access to a JIRA instance if it is not using SSL.
 
+**Since the version 2.0.18, SSL certificate verification is mandatory due to Splunk Cloud vetting requirements.**
+
 **When using SSL, there might be different conditions:**
 
 - The SSL certificate is from an official third party certificate authority and it is valid, you normally can tick the SSL validation box which enforces the fact that we expect the certificate to be valid. If the certificate is not valid, we will not allow any action to be performed.
diff --git a/docs/releasenotes.rst b/docs/releasenotes.rst
index b0afa20..033c829 100644
--- a/docs/releasenotes.rst
+++ b/docs/releasenotes.rst
@@ -1,6 +1,22 @@
 Release notes
 #############
 
+Version 2.0.18
+==============
+
+- Fix Issue#184 - Fix - Splunk Cloud vetting - Force SSL Verification or the use of a CA bundle to validate the SSL verification #184
+- Fix Issue#185 - Build - Prevents pyc, hidden files or directory to be part of the release #185
+- Fix Issue#186 - Pypi requirements libs refresh #186
+- Fix Issue#188 - Number of projects count in Overview - JIRA Projects is wrong #188
+- Fix Issue#189 - Avoid app nav bar ending in multiple lines #189
+
+Version 2.0.17
+==============
+
+- enhancement - Custom fields - Add additional protection against badly parsed custom fields #174
+- enhancement - Allows adding the Splunk search results in the JIRA Description field (in CSV or JSON format) #173
+- bug - Splunk Cloud Classic - ensures that indexed time parsing is partioned on the Search Heads properly (SLIM) #176
+
 Version 2.0.16
 ==============