Agenda:

...

1. Release docker versions v2.2.0 - Manoop - send email to LF team

...

1. Casablanca goals are being defined here https://wiki.onap.org/display/DW/Casablanca+goals
2. Any new proposals for Code Committer role?Code Coverage needs to be improved to 80% - require TechM and IBM resources to commit for the plan
   1. Sireesh to get back on the resource plan for code coverage from IBM. (may be on SDK repo ); - Naveen is working this. Plan the files that Naveen can cover in SDK (Hima to work with Naveen).update on the SDK coverage?
   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 ( from Robert) plugin like jacoco - ?? ; check out this webpage https://blog.akquinet.de/2014/11/25/js-test-coverage/ ; for  examples see https://github.com/webpack/webpack/tree/8b19f20b40f7942856e3091e15394e9abca87b24/test (from Lorraine)
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 - Mon June 11 - Sireesh to send the meeting invite
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 - plan is to submit new commit?
5. MUSIC jar 2.5.5 is missing and failing Jenkins jobs.
6. 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

Attendees:

Image RemovedSaravanan, Sireesh, Farhan, Lorraine, Prasad

Discussion Items:

1. OOM integration and enhancement plans for Casablanca - Manoop/Sunder
   1. deployment, scalabilty of the platform issues (Start creating user stories based on the design review)
   2. Music as a service - integration? - Sunder
2. AAF integration plan for Casablanca - Sunder/Farhan/Manoop
   1. Truning ON AAF and starting using role management for partners
   2. AAF certificate management integration (both for FE HTTPs and BE rest API calls)
3. Security issues from Nexus-IQ plan for Casablanca - Farhan
   1. Angular will be a problem - How can we upgrade Angular - Saravanan
   2. Possibly in phases - In casablanaca, start remiving removing the vulnerabilities that are maeked as - "Not vulnerable in ONAP" 
   3. Fix pending Fortify issue
4. Internationalization language support plan for Casablanca - PORTAL-267 - Leimeng to followup
   1. Choose language/internal components
   2. In discussion by larger community (Use Case UI Team), expecting implementation details
   3. Leimeng has sent email to Tao Shen shentao@chinamobile.com on this topic and is waiing fr his return email
5. Lorraine to run grep scan for ecomp keyword  - done - Review with Sunder/Manoop - will send them result in email
6. Performance Docker JVM memory - SunderAPI Versioning and Backward Compatibility (Technical Debt)
7. Performance 
   1. Memory usage optimization
   2. Split DB, Portal and SDK docker images plan for Casablanca - Robert working on it
   3. UI upgrades - Angular, Bower
   4. Simplify deployment by avoiding the etc/hosts file entries
8. Testing
   1. CSIT test for new Casablanca features - Sunder to schedule a session to go over the new features.
   2. Convert ECOMP selenium tests into CSIT ONAP Robot Framework tests - Sunder/Sireesh
   3. Enable JavaScript Unit tests. (How will this impact the angular upgrade? Will these unit tests work as is even after upgrade?)
   4. Code Coverage needs to be improved to 80% on both portal and portal/sdk repos.
9. Defect fixes
   
   
   

Beijing Release Planning:

1. M0 - dev kick-off, Nov 16
2. M1 - planning Jan 16
3. M2 Functionality Freeze 12 Feb 2018 →  fill in the contents by Manoop & Leimeng - done
4. M3 API/Data Model Freeze 08 Mar 2018
5. M4 Code Freeze 29 Mar 2018
6. RC0 Checklist19 Apr 2018
7. RC1 Checklist 03 May 2018
8. RC2 Checklist 31 May 2018
9. Release Delivery 07 Jun 2018

...