Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Agenda:

  1. Review status on items assigned to dev team
  2. Go over JIRA list assigned for Beijing release
  3. Discuss M1 planning and check list for Beijing release

...

Chris Lott, Giri, WeitingLeimeng ShiSunder Tattavarada, BINDU ELISETTY, HIMA (hbindu@research.att.com), Farhan Mir

Discussion Items:

  1. Who is the replacement for testing lead? - Leimeng to followup
  2. Portal-151 - followup with usecaseui and schedule a session to review the architecture - Leimeng
  3. Portal-182 - CLI integration help - Leimeng to setup a working session - Sunder Tattavarada/Former user (Deleted)
  4. Portal-155 - security issues scan - Farhan/Sunder
  5. Plan to release SDK 2.1.0 version and then communicate to partners to update their poms - Sunder/Leimeng - ETA 1/17.
  6. Extend Portal-119 to split DB for Portal and SDK - Robert - provide ETA by 1/11
  7. Sent grep scan on "master_dev" branch to check if "ecomp" appears in Portal - done - Hima will be cleaning up - ETA 1/10.
  8. SDK will be next to scan - Lorraine - ETA 1/11
  9. Split Portal-19 to Hima and Robert (based on Lorraine's scan output)  - create tasks based on the scan - Robert to analyze the font "Omnes-ECOMP-W02".
  10. JUnit /Sonar coverage to 50% on SDK and Portal. ( 
    1. SDK - JUnit test coverage from 4% to 50% - Hima (pending code review and push to gerrit)
    2. Portal - target 30% to 50% - Giri (to coordinate with Hima to find the right code modules)
  11. Discussed remaining JIRA items in great details
  12. M1 due on 1/818/2018 (same template as Amsterdam) - Manoop/Leimeng
  13. Check with IBM team members - Manoop/Abbas/Sunder
  14. Beijing Release Planning:
    1. M0 - dev kick-off, Nov 16
    2. M1 - planning Jan 16
    3. M2 -  functionality freeze Feb 15
    4. M3 - API freeze Mar 1
    5. M4 - code freeze Apr 5

...