Versions Compared

Key

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

...

 

  • TSC approves any requirement marked as "Green" as "GO" for M4

August 

 

  • TSC agreed that only GPL v3 should be removed from the containers for the Guilin Release, distributed by the ONAP Community
  • TSC approves any requirement marked as "Green" and "Yellow" as "GO" for M2/M3 
  • TSC approved CLAMP, SDNC/CCSDK, Holmes projects as successfully passing their M2/M3 milestones.

...

  • TSC approved the re-election of Magnus Buhrgard as our ONAP Network Management Technical Community Coordinator - https://lists.onap.org/g/onap-tsc-vote/message/1814
  • TSC approved PTL Toolchain Improvements - Short Term Path - https://lists.onap.org/g/onap-tsc-vote/message/1815
  • TSC approved that permissive and weak copyleft licenses can be part of ONAP containers - https://lists.onap.org/g/onap-tsc-vote/message/1816
  • TSC approved the new Policy Committer - Ajith Sreekumarhttps://lists.onap.org/g/onap-tsc/message/6869
  • TSC approved during the TSC Call - TSC 2020-07-23
    • The changes to the TCC positions; Removal of Infrastructure Coordinator, align 5G and Edge to the Requirements Subcommittee, Cloud Native to the CNF Taskforce, and AI/ML to the Control-loop subcommittee.
    • TSC approved Option 1 concerning Non Functional Requirements i.e. Approve all the non functional requirements for M1 so the project teams can try to improve during the Guilin timeframe until M4 (Code Freeze)
    • TSC approved M1 Guilin Milestone including REQ335-338
    • TSC approved with the recommended promotion of AAI, CCSDK, DCAE, DMaaP, ExtAPI, Modeling, OOF, Policy, SDC, SO & UUI from the "Incubation" to "Mature" project state.
    • TSC agreed with the recommendation that the following projects have not met the criteria for promotion at this time: CLAMP, CLI, Holmes, Portal & VVP

...

 TSC approved the following priorities #1 Completion of Frankfurt and #2 Kick-off Guilin release, does the TSC approve an El-Alto Maintenance release just after Frankfurt Sign-Off TSC 2020-06-04

TSC approved to cancel the TSC Call on June 25th, 2020 (LFN Event/Public Holiday in China) -  https://lists.onap.org/g/onap-tsc-vote/message/1635

...

TSC approved the creation of a new repository for the Integration Team (robot-utils) - https://lists.onap.org/g/onap-tsc/message/6521

 TSC 2020-06-11

  • Resolved: That the TSC approves for the Frankfurt release, as exceptions to the Intellectual Property Policy in the ONAP charter, the non-Project Licenses described in the license scan report attached to the email https://lists.onap.org/g/onap-tsc-private/message/1020 distributed to the TSC on May 28, 2020; excluding the exceptions described as not requested or required in the attached report.
  • #AGREED: the TSC signs-off on the Frankfurt release based on the following conditions
    #1 Feedback from PTLs about new issues CCSDK-2425, CCSDK-2399 and Policy-2631 by June 12th EOD - work around on top of RC2 dockers and/or new patch post-Frankfurt Self-Release
    #2 UseCase/Functional reqs owners to confirm by Monday June 15th that they maintain their requirements or not, accepting the risk that final regression on RC2 dockers will continue after the sign-off

 TSC 2020-06-18 #AGREED anybody can build a POC. It is always appropriate to share the intent of the PoC with the TSC  early to facilitate inclusion in a future release.  

...

New Frankfurt RC2 date, May 26th, has been approved by the TSC - https://lists.onap.org/g/onap-tsc-vote/message/1573

 TSC 2020-05-14

  • The TSC approved of proceeding with using El Alto containers for ESR for the Frankfurt release only and granting a waiver for the security issues (option #1 from Jimmy’s email) in case of the non-root pod can't be solved by May 18th EOD. If it is can not be solved by May 19th morning then the TSC approves option #1 with the conditions that ESR cross-components impact will be identified and fixed prior as a maintenance patch on top of Frankfurt release".

...

 TSC 2020-05-28 TSC agreed to descope "Document current component upgrade strategy" from Frankfurt AND Descope CII Badging requirement from Frankfurt AND combine the RC2 and Sign-off milestones

...

TSC confirmed Olivier Phénix as the replacement for the reserved seat vacated Alexis de Talhouët  https://lists.onap.org/g/onap-tsc-vote/topic/71636263#1426
Requirements, Use Cases [ marked as ] GREEN [ in Frankfurt Release Requirements  ] Approved by TSC [  (applies to v552  https://wiki.onap.org/pages/viewpage.action?pageId=81397959 ) ]  TSC 2020-03-05

  TSC agreed that the following projects have successfully completed the requirements for Frankfurt M4:  CLAMP, ExtAPI, Modeling, Policy, VID, VVP, VNFReqs  https://lists.onap.org/g/onap-tsc/topic/71404800#5940

  TSC confirmed Dong Wang  as the replacement for the reserved seat vacated by Huang ZongHe   https://lists.onap.org/g/onap-tsc-vote/topic/71728172#1465

 TSC 2020-03-12

  • TSC approved of the following projects for Frankfurt M4: AAI, DCAE, SDNC, VFC, SO, MultiCloud 
  • TSC approved the following requirements  REQ-140 IN PROGRESS REQ-37 IN PROGRESS REQ-150 IN PROGRESS ,  REQ-84 IN PROGRESS REQ-118 IN PROGRESS REQ-129 IN PROGRESS REQ-76 IN PROGRESS REQ-174 IN PROGRESS REQ-215 TO DO REQ-219 IN PROGRESS  &  REQ-227 IN PROGRESS  as documented in v572 of the Frankfurt Release Requirements.   
  • TSC approved on 3/12/2020 the following SECCOM/PTL requests for the Frankfurt release: Best effort on OJSI tickets for Frankfurt, except for REQ-231 is mandatory with some exceptions

...

  TSC approved the “ONAP Automation Testing - Portal/SDC” and the “ONAP Security Requirements – SDC” [ intern ] projects to be part of the 2020 Mentorship Program https://lists.onap.org/g/onap-tsc-vote/topic/71934281#1483

  TSC 2020-03-19

  • TSC approved granting a waiver for the Portal project for 
    Jira
    showSummaryfalse
    serverONAP JIRA
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyREQ-64
    for the Frankfurt release
  • TSC agreed to the following- 1) list from SECCOM, [ owned by SECCOM ]  2) plan forward, [ owned by Release Manager ] 3) resume project review "MVP", [ owned by Chaker Al-Hakim & Jason Hunt ]  4) ensure that all issues are OK by RC0. [ evaluation owned by the Integration team ]
  • TSC agreed new repository creation request for the bbs use case

  TSC 2020-03-26

  • Frankfurt Release – M4 Code Freeze was successfully completed after the approval by the TSC of the remaining projects and requirements:
    • TSC approved the following projects for M4:  APPC, CCSDK, Integration, MSB, OOF, OOM, SDC, UUI, VNFSDK, PORTAL, MUSIC, AAF 
    • TSC approved the following requirements for M4:
      Jira
      showSummaryfalse
      serverONAP JIRA
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId425b2b0a-557c-3c0c-b515-579789cceedb
      keyREQ-267
      Jira
      showSummaryfalse
      serverONAP JIRA
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId425b2b0a-557c-3c0c-b515-579789cceedb
      keyREQ-223
      Jira
      showSummaryfalse
      serverONAP JIRA
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId425b2b0a-557c-3c0c-b515-579789cceedb
      keyREQ-231
      Jira
      showSummaryfalse
      serverONAP JIRA
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId425b2b0a-557c-3c0c-b515-579789cceedb
      keyREQ-235
      Jira
      showSummaryfalse
      serverONAP JIRA
      serverId425b2b0a-557c-3c0c-b515-579789cceedb
      keyREQ-239
       & 
      Document current upgrade strategy 
    • TSC descoped
      Jira
      showSummaryfalse
      serverONAP JIRA
      serverId425b2b0a-557c-3c0c-b515-579789cceedb
      keyREQ-64
       from the Frankfurt release and waiving  
      Jira
      showSummaryfalse
      serverONAP JIRA
      serverId425b2b0a-557c-3c0c-b515-579789cceedb
      keyOJSI-190
       and requires the vulnerability to be published in the release notes.
  • TSC agreed that 
    Jira
    serverONAP JIRA
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyPORTAL-849
     is a blocker for the Frankfurt release
  • TSC approved moving the RC0 date to April 2nd 
  • TSC approved both repos are approved pnf-simulator and mdons use case 
  • TSC approved archiving the doc/tools repo

February

  TSC 2020-02-06

  • TSC approved the response to the 3 requests from 3GPP as outlined on slide 3 of the "TCC Generic Network Management_Prague_3GPP SA5_LS.pdf" deck as attached to these minutes.
  • TSC approved that the following requirements
    Jira
    showSummaryfalse
    serverONAP JIRA
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyREQ-140
    ,
    Jira
    showSummaryfalse
    serverONAP JIRA
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyREQ-134
    ,
    Jira
    showSummaryfalse
    serverONAP JIRA
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyREQ-76
    ,
    Jira
    showSummaryfalse
    serverONAP JIRA
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyREQ-174
    and "Modeling: documentation of allotted resource model" as being in the Frankfurt release.
  • TSC descoped
    Jira
    showSummaryfalse
    serverONAP JIRA
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyREQ-136
    from the Frankfurt release.
  • TSC approved all projects that have met Frankfurt M2/M3 milestone requirements since last week.
  • TSC approved SonarCube decommission on Feb 20

...

 The TSC approved the ReadTheDocs versus Wiki usage policy https://lists.onap.org/g/onap-tsc-vote/topic/71405726#1381

 TSC 2020-02-27 

  • TSC approved that code coverage criteria for M4 is removed AND migration to SonarCloud must be completed by RC0 and the test coverage value should be at 55%
  • The TSC stipulate that migration to Portal SDK 2.6 (by any impacted projects) is a pre-requisite for meeting the M4 milestone delivery for the Frankfurt release https://lists.onap.org/g/onap-tsc-vote/message/1369 
  • TSC agreed to use the proposed updates from @Lingli for the LF Board update

...

 cancel/maintain the TSC call on January 23rd, 2020 (lunar new year) https://lists.onap.org/g/onap-tsc-vote/topic/69956823#1351

  TSC 2020-01-30

...