Agenda:

1. Casablanca goals are being defined here https://wiki.onap.org/display/DW/Casablanca+goals
2. Code Coverage needs to be improved to 80% - require TechM and IBM resources to commit for the plan
   1. SDK repo - Naveen is working this. New SDK commits made - Please add more reviewers. 
   2. Prasad/Swapnali - Please use Epic - PORTAL-268 - for code coverage - PORTAL-273; for sonar issues - PORTAL-247; (focused on Portal repo).
   3. Portal's Javascript unit test plan? Yes it should be done in Casablanca- Prasad/Swapnali (Manoop to followup with TSC on the requirement on JS code coverage), Karma - look into it (Yatindra looking into it) plugin like jacoco
   4. Code Coverage: recommendation from TSC is to keep 50% Code Coverage for Casablanca including JavaScript. (In Beijing Release code coverage was only covering Java and Python code)
3. Design for Angular update - Saravanan to provide the Design review and plan; listed out items, testing one screen, needs a week for this , another week for design document
   1. Portal Admin screen - for POC to migrate to latest Angular - Saravanan (Design discussion to understand the impact - Thurs 05/31).
   2. Demo with one screen with Angular 5, Karma testing - Demo shown to Sunder
   3. Bring up the application with Angular 1 and latest version 5 - Saravanan (Analysis: move away from bower and use node. Trying in portal with FE and BE).
   4. Should we split SDK FE and BE? - need more discussion and impact analysis.
   5. Estimate of the migration to latest Angular - Saravanan
   6. fonts and icons abstraction so that they can be switched with a flag configuration - Saravanan (decided to achieve this configuration during the build rather than at runtime).
4. SDK code coverage dropped to 49% on master - every new code commit from any developer must make sure that that the code coverage remains same and improves - Kishore to push the code coverage mostly related to AAF changes. - The latest commit is abandoned - new commit is submitted (https://gerrit.onap.org/r/#/c/51087/) - it is under review (verify the comments under the abandoned commit are addressed - here is the abandoned commit - https://gerrit.onap.org/r/#/c/49785/).
5. Lorraine to run grep scan for ecomp keyword  - done - Review with Sunder/Manoop - will send them result in email
   1. Look for the vm host names in the files - to clean up - Lorraine already made commit for this changes - Hima can help if requires java file changes.
6. Design to be scheduled for Simplify etc/hosts, OOM and AAF changes - Sunder (forward to Ritesh Nadkarni and team too)
   1. Leimeng to schedule the AAF review session for Casablanca changes

7. Award nominations - ONAP Community Awards: Beijing Release - Nominations: Close 6 PM Pacific time, June 14 - Voting will take place June 15 -- 19

8. VM11 test environment xDemo app access issue - Leimeng to verify

9. 
   

   HEAT-based ONAP deployment support should be dropped once OOM-based ONAP deployment's issues are fully identified and resolved.

   
   

   Recommendation from TSC: keep supporting HEAT in Casablanca for testing and integration purposes. However, HEAT won't be a gating item at Release Sign-Off.

10. Platform Maturity - S3P goal: Absolute Minimum expectation:

    
    

    • CII badging passing level
    • Continuously retaining no critical or high known vulnerabilities > 60 days old
    • All communication shall be able to be encrypted and have common role-based access control and authorization.

    
    

    Desired expectation is full CII badging silver level, if not 75% towards that.

    
    

...

Casablanca Release (Nov 2018)

• M1 Release Planning 28 Jun 2018
• M1 Release Planning Checklist  28 Jun 2018
• M2 Functionality Freeze 26 Jul 2018
• M3 API/Data Model Freeze 23 Aug 2018
• M4 Code Freeze 20 Sep 2018
• RC0 Checklist 11 Oct 2018
• RC1 Checklist 25 Oct 2018
• RC2 Checklist 08 Nov 2018
• Release Delivery 15 Nov 2018

...