David McBride

Honolulu Release (RC0) - NO GO & remaining M3 tasks - NO GO(completed)

• Krzysztof Opasiak reports blocking issue for RC0:
  • I believe that we'll be unable to meet RC0 tomorrow as we've a bug in
    the master branch and we're investigating it together with the
    integration team but until it is found we had to hold off OOM merges so
    that we don't merge code blindly .- Need time to solve but no more a blocker
  • Helm Chart v3.0 is causing some issues for some projects - Shall we setup a War Room?
    • Documentation Guide: https://docs.onap.org/projects/onap-oom/en/latest/oom_quickstart_guide_helm3.html
      
    • Add details about to handle the Master branch 
    • PTL to open OOM JIRA ticket is any additional issue is identified
  • Gating not running well since 3/9 ?- Seems back to normal.
• Honolulu Milestone Status
  • M3 exceptions - 100% Completion (Projects & Requirements); 
  • RC0 - 73% 76% completion and Requirements Status: 51 55% completion
    • Show where RC0 Scorecard is
    • Marketing updates from the Req. Owners should highlight the benefits brought by their requirement from an E2E perspetive - see existing samples
    • Honolulu Release Integration Testing Status
• Honolulu Milestone and Requirements Exception Requests
• #AGREED the TSC approves slipping the date for Honolulu RC0 and all following milestones by 1 week (March 18) . The new release date for Honolulu will be April 8th.
  

Next Steps

#1 Honolulu Release Key Updates - Marketing Team is expecting to get feedback from Subcommittees, Req. Owners + Doc, Integration and OOM projects

#2 Do not forget to document the use case, feature and spec as part of the release note by the project (RC1 task?) - Improvement area for Istanbul i.e. Create *.rst file as part of Requirement submission or other suggestion so we do not lose what Req owners provided at earlier stage

•  Action (Doc/Architecture Subcommittees): Define how use case, feature and spec should be documented and be part of the release note

#3 Add RC0 tasks for REQ-400

Requirement Subcommittee to follow-up with requirement owners to clean up their RC0 tasks

no later than 11/17 EOD

Istanbul Release

• Roadmap Proposal
• Add a milestone 1 week before M3 –  to ask ONAP Contributors to submit their final code change so it gives 1 week for each project team to finalize their packaging
• TSC VoteA new milestone has been added to address concerns raised by PTLs on 3/4 i.e. M3-Final Code Submission prior M4 Feature Freeze
• No TSC Vote today but let's PTL/Req. Owners and the ONAP Community to provide additional feedback during the PTL Call on 3/15.

Jessica Gonzalez

Vijay Kumar

cl664y@att.com

Kenny Paul

Amar Kapadia

ONAP support to LF OPS 5G project  

• Amar Kapadia will present test bed in progress being setup so DARPA
• OPS-5G Use case presentation postponed to March 31st, 2021 at 7am PST (previously scheduled on 3/17)

cl664y@att.com

Thank you Davide Cherubinifor all your great contributions to the ONAP Community as TSC Member, MAC representative and more !

Remaining Guilin Awards: Top Achievement Award, Citizen Award and S3P Award

Kenny Paul