State that Casablanca is not security maintained

According to recently updated Vulnerability Management Procedure we
are going to develop security fixes for master and the latest release.
Following TSC recommendation Casablanca release is excluded from that
rule.

In order to make community fully aware of that, let's add this info to
Cassablanca release notes.

Issue-ID: SECCOM-216
Change-Id: I3c1d963c1c97535160455b1e363b5bf979fc2a25
Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com>

diff --git a/docs/release/index.rst b/docs/release/index.rst
index 275567c..0423936 100644 (file)
--- a/docs/release/index.rst
+++ b/docs/release/index.rst
@@ -195,11 +195,14 @@ The goal of the Casablanca release is for all ONAP projects to be close to achie
 
 Project specific details are in the :ref:`release notes<doc-releaserepos>` for each project.
 
+**Please note that according to `TSC recommendation <https://lists.onap.org/g/onap-seccom/message/1080>`_ Casablanca release is not supported in terms of security bug fixes.
+It means that community is not going to backport any security fixes developed during Dublin or any later release cycle to this release.**
+
 .. index:: maturity
 
 ONAP Maturity Testing Notes
 ===========================
-For the Casablanca release, ONAP continues to improve in multiple areas of Scalability, Security, Stability and Performance (S3P) metrics.\r
+For the Casablanca release, ONAP continues to improve in multiple areas of Scalability, Security, Stability and Performance (S3P) metrics.
 
 The Integration team ran the 72 hours stability testing (100% passing rate) and full resilience testing (96.9% passing rate) at ONAP OpenLabs. More details in :ref:`ONAP Maturity Testing Notes <integration-s3p>`
 
@@ -237,4 +240,3 @@ To properly report a bug in Jira, you may want to consider these `recommendation
 
    releaserepos.rst
    repolist.rst
-