From 494cba66fa0b6011473059248adc0b4cec0e1e36 Mon Sep 17 00:00:00 2001 From: Gildas Lanilis Date: Fri, 17 Nov 2017 16:38:41 -0800 Subject: Update Master Release Notes -Chnage procedure to report a bug for non expert -Update platform requirement Issue-Id: DOC-150 Change-Id: I2abd23af2e5f435cd3c34cb7867a93063c520f57 Signed-off-by: Gildas Lanilis --- docs/release/index.rst | 26 ++++++++++---------------- 1 file changed, 10 insertions(+), 16 deletions(-) (limited to 'docs/release') diff --git a/docs/release/index.rst b/docs/release/index.rst index 4e552d76b..8606de3e9 100644 --- a/docs/release/index.rst +++ b/docs/release/index.rst @@ -95,10 +95,10 @@ Each project provides detailed :ref:`release notes` and prepends to these if/when any updated versions the project team believes are compatible with a major release are made available. -Supported Platforms -+++++++++++++++++++ -ONAP Amsterdam Release has been tested on Ubuntu 16.04 and thus is -the only OS supported. +Platforms Requirements +++++++++++++++++++++++ +ONAP Amsterdam Release has been tested on Linux OSs. Details are `available here `_. + .. index:: Download @@ -112,13 +112,11 @@ There are 3 approaches to install ONAP: Full ONAP installation using Heat template ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -From a complete demo solution perspective. This installs the whole ONAP, - refer to :ref:`Setting Up ONAP `. +From a complete demo solution perspective. This installs the whole ONAP, refer to :ref:`Setting Up ONAP `. Advanced installation to install individual components ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -From a developer perspective. ONAP can be installed component per component: - :ref:`installation is listed in `. +From a developer perspective. ONAP can be installed component per component, refer to :ref:`the installation procedure available for each component`. * The list of ports used by default within ONAP is documented in `ONAP Service List `_. * The ONAP Source Code is available through Gerrit at https://gerrit.onap.org or Git at https://git.onap.org/. @@ -165,9 +163,7 @@ ONAP Amsterdam Documentation is licensed under the `Creative Commons Attribution Known Issues and Limitations ++++++++++++++++++++++++++++ -Known Issues and limitations are documented in each project Release Notes. - -Refer to :ref:`release notes ` for each project. +Known Issues and limitations are documented in each :ref:`project Release Notes `. .. index:: Reporting Bugs @@ -175,12 +171,10 @@ How to Report a Bug +++++++++++++++++++ There are 2 ways to report a bug in ONAP. - * In case you are familiar within ONAP, you can directly - report a bug by creating a Jira issue - at `ONAP Jira `_. + * In case you are familiar within ONAP, you can directly report a bug by creating a Jira issue at `ONAP Jira `_. - * If you don't know you are facing a bug or have a question, email - the ONAP Discuss mailing list at onap-discuss@lists.onap.org . + * If you don't know you are facing a bug or have a question, post your question into the `Ask question `_. +You will need a Linux Foundation ID to login and post your question. Get a Linux Foundation Identity using this `quick procedure `_. You may consider these `recommendations `_ to elaborate the issue you are facing and this `guideline `_ to register into the ONAP Discuss mailing list. -- cgit 1.2.3-korg