January
1/3 TSC Call
...
- The Vulnerability Management Procedure (ONAP Vulnerability Management v22) has been approved. The e-mail notification should be sent to Kenny Paul, Jim Baker and TSC Chair -https://lists.onap.org/g/onap-tsc-vote/message/836
...
- TSC approves the M3 Modeling Checklist as a non-blocking item -"Has the Project team provided links to Data Models (e.g, JSON, YANG, Swagger, etc.) for all Shared Information (e.g., APIs, API Payload, Shared Design Model)?""
- TSC approves the Modeling proposal - Modeling subcommittee reached consensus on "Non MANO set identifier definition in VNF/PNF onboarded package and registration in ETSI NFV"
3/13
- The TSC adopts UTC as the official time zone for scheduling meetings and conducting business for all projects. All ONAP calendar entries are created using UTC start times and not to created using any local time zones. https://lists.onap.org/g/onap-tsc-vote/message/837
3/14 TSC Call
- Dublin API Freeze (M3) has been approved by the TSC
- TSC Policy on ONAP Maintenance Release has been approved by TSC - ONAP Maintenance Policy
...
- TSC approves that the tsc mailing list ('onap-tsc@lists.onap.org') will be used as point of contact for Non-MANO artifact registration in ETSI
April
TSC agrees the ONAP Release Manager recommendations about M4 i.e. NO-GO, to be reviewed on 4/18
- Dublin Code Freeze (M4) has been approved by the TSC with gating conditions
- TSC Agree that any requirement (use case, functional requirement, non-functional requirement), currently marked in yellow/(red), not due to testing blockers/issues, will be moved to the POC section a.k.a no more be part of the official release, if no feedback provided to Jim by 4/22 EOD
- TSC agree that RC0 will shift to May 2nd with the condition that a clear plan is built at RC0 to complete the release considering the reduced scope.
- The list of Open Source External Coordinators has been approved by the TSC - https://lists.onap.org/g/onap-tsc-vote/message/917
- ONAP El-Alto Schedule/Focus & ONAP Frankfurt Release Milestones have been approved by the TSC -https://lists.onap.org/g/onap-tsc-vote/message/919
...
- TSC recommended to the Security Subcommittee to perform a risk assessment, similarly to what it is currently performed for the License issues on a release basis, so the TSC can make a GO/NO GO decision from a Security perspective
- TSC approved new Documentation Committer: Andreas Geissler (DT)
- TSC agreed that Olivier Phenix will be the proxy for Alexis de Talhouët (BELL TSC reserved seat) until BELL internally settle on who should be the right person given the “Active community member” requirements.
- TSC agreed to stick with the current TSC composition for the next election. https://lists.onap.org/g/onap-tsc-vote/message/1171
- TSC has signed-off on the El-Alto Release
- TSC approved the Proposal for PNF software version in PNF upgrade in Frankfurt release
- TSC approved the POC definition - https://lists.onap.org/g/onap-tsc-vote/message/1242
- TSC agreed to cancel the TSC meeting on Nov 28th - https://lists.onap.org/g/onap-tsc-vote/message/1240
- TSC agreed to cancel the TSC meeting on Dec 25th - https://lists.onap.org/g/onap-tsc-vote/message/1239
- TSC agreed to cancel the TSC meeting on Jan 1st, 2020 - https://lists.onap.org/g/onap-tsc-vote/message/1241
- TSC provided the Frankfurt prioritization - Frankfurt Release Requirements
...
- Use Case Approach Evolution Proposal (vote in progress extended till 12/17 EOD)
- Remediating known vulnerabilities in third party packages (vote in progress till 12/17 EOD)
- Chaker's proposal (under discussion)