1 .. This work is licensed under a Creative Commons Attribution 4.0 International License.
2 .. http://creativecommons.org/licenses/by/4.0
8 Initial Release for Frankfurt
13 :Release Date: 2020-05-20
17 - MUSIC now runs on a springboot server, instead of a standalone tomcat server
19 - HTTPS support for clients through AAF certificates
21 - A background lock clean up daemon will periodically check the status of current locks, cleaning up 'stale' references.
22 Clients should see a performance boost if they were previously dealing with many stale locks.
24 - Improved error messaging to the user, allowing clients to better debug their applications
26 - Continued adherence to ONAP S3P requirements
30 - `MUSIC-573 <https://jira.onap.org/projects/MUSIC/issues/MUSIC-573`_ Pods still run as root
32 - `MUSIC-557 <https://jira.onap.org/projects/MUSIC/issues/MUSIC-557`_ Test coverage goals met, and migrated to new sonar location
34 - `MUSIC-530 <https://jira.onap.org/browse/MUSIC-530>`_ Security Vulnerability in pom.xml fix
43 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>`_.
47 - `MUSIC project page <https://wiki.onap.org/display/DW/MUSIC+Project>`_
48 - `MUSIC Frankfurt Release <https://wiki.onap.org/display/DW/MUSIC+Frankfurt>`_
49 - `Passing Badge information for MUSIC <https://bestpractices.coreinfrastructure.org/en/projects/1722>`_
50 - `MUSIC Architecture Page <TBD>`_
51 - `Project Vulnerability Review Table for MUSIC <https://wiki.onap.org/pages/viewpage.action?pageId=64004601>`_