diff options
Diffstat (limited to 'docs/release-notes.rst')
| -rw-r--r-- | docs/release-notes.rst | 63 |
1 files changed, 42 insertions, 21 deletions
diff --git a/docs/release-notes.rst b/docs/release-notes.rst index 9b6688c3..5e8885da 100644 --- a/docs/release-notes.rst +++ b/docs/release-notes.rst @@ -1,50 +1,71 @@ -.. This work is licensed under a Creative Commons Attribution 4.0 International License. +.. This work is licensed under a +.. Creative Commons Attribution 4.0 International License. .. http://creativecommons.org/licenses/by/4.0 +.. _release_notes: Release Notes ============= +Initial Release for Frankfurt -.. note:: - * This Release Notes must be updated each time the team decides to Release new artifacts. - * The scope of this Release Notes is for this particular component. In other words, each ONAP component has its Release Notes. - * This Release Notes is cumulative, the most recently Released artifact is made visible in the top of this Release Notes. - * Except the date and the version number, all the other sections are optional but there must be at least one section describing the purpose of this new release. - * This note must be removed after content has been added. +Version: 3.2.40 +--------------- +:Release Date: 2020-05-20 -Version: x.y.z --------------- +**New Features** +- MUSIC now runs on a springboot server, instead of a standalone tomcat server -:Release Date: yyyy-mm-dd +- HTTPS support for clients through AAF certificates +- A background lock clean up daemon will periodically check the status of + current locks, cleaning up 'stale' references. + Clients should see a performance boost if they were previously dealing with + many stale locks. +- Improved error messaging to the user, allowing clients to better debug their + applications -**New Features** +- Continued adherence to ONAP S3P requirements -One or two sentences explaining the purpose of this Release. **Bug Fixes** - - `CIMAN-65 <https://jira.onap.org/browse/CIMAN-65>`_ and a sentence explaining what this defect is addressing. + - `MUSIC-573 <https://jira.onap.org/projects/MUSIC/issues/MUSIC-573>`_ Pods still run as root + + - `MUSIC-557 <https://jira.onap.org/projects/MUSIC/issues/MUSIC-557>`_ Test coverage goals met, and migrated to new sonar location + + - `MUSIC-530 <https://jira.onap.org/browse/MUSIC-530>`_ Security Vulnerability in pom.xml fix + + + **Known Issues** - - `CIMAN-65 <https://jira.onap.org/browse/CIMAN-65>`_ and two, three sentences. - One sentences explaining what is the issue. - - Another sentence explaining the impact of the issue. - - And an optional sentence providing a workaround. +N/A + +**Security Notes** + +MUSIC code has been formally scanned during build time using NexusIQ and all Critical vulnerabilities have been addressed, items that remain open have been assessed for risk and determined to be false positive. The MUSIC open Critical security vulnerabilities and their risk assessment have been documented as part of the `project <https://wiki.onap.org/pages/viewpage.action?pageId=45285410>`_. -**Security Issues** - You may want to include a reference to CVE (Common Vulnerabilities and Exposures) `CVE <https://cve.mitre.org>`_ +Quick Links: +- `MUSIC project page <https://wiki.onap.org/display/DW/MUSIC+Project>`_ +- `MUSIC Frankfurt Release <https://wiki.onap.org/display/DW/MUSIC+Frankfurt>`_ +- `Passing Badge information for MUSIC <https://bestpractices.coreinfrastructure.org/en/projects/1722>`_ +- `MUSIC Architecture Page <TBD>`_ +- `Project Vulnerability Review Table for MUSIC <https://wiki.onap.org/pages/viewpage.action?pageId=64004601>`_ **Upgrade Notes** + N/A + **Deprecation Notes** + N/A + **Other** + N/A + =========== End of Release Notes |