2021 TSC Decisions

Dec

#AGREED the TSC approves remediating log4j as the top priority for the ONAP community requiring immediate action to correct in both Istanbul and master branches.
#AGREED The log4j vulnerability will mandate an Istanbul maintenance release. The maintenance release should be limited to log4j remediation only.
#AGREED OK for RelEng to proceed with the JCasC migration today
#AGREED the TSC approves the Istanbul Award definitions

#AGREED the TSC approves the Jakarta release as having met the M1 milestone with the condition that the M1 tasks for the E2E Network slicing use case are to be closed by M2.
#AGREED ok to archive the dmaap/mirroragent repo.
#AGREED the TSC accepts the results of the Modeling Subcommittee nominations as sufficient to certify @Xu Yang and @guochuyi as new ONAP Modeling Subcommittee Co-Chairs.

#AGREED M1 for Jakarta will be moved to Dec 9, 2021 with remaining milestones to remain as-is
#AGREED the TSC approves the promotion of
REQ-441 - LOGS MANAGEMENT - PHASE 1: COMMON PLACE FOR DATA from Best Practice to A Global Requirement (tracked as
for Jakarta) and
REQ-1072 - Standardized logging fields and
REQ-1073 - Using basic image from Integration to be established as Best Practices beginning with Jakarta

#AGREED Release sign off scheduled for Nov 15, 2021 at the PTL meeting. TSC attendance is required.

#AGREED the TSC approves the Jakarta release schedule (v.5) of https://wiki.onap.org/x/VIKfBg

#AGREED the TSC approves the following recommendations: 1) Approve RC milestone with condition that remaining release management tasks are resolved by Sign Off. 2) Move Sign Off out one week to Nov 4

#AGREED the TSC approves the Honolulu maintenance release with the component level release notes for CCSDK, Multicloud, OOM & OOF to be completed by Oct 8, 2021
#AGREED the TSC approves the Jakarta release schedule as presented today in (v. 3) of https://wiki.onap.org/x/VIKfBg with the actual publishing of the schedule to be held in draft pending the outcome of the agile transformation workshop

#AGREED: the way forward for Best Practice & Global Requirement tracking will be:
- Istanbul: SECCOM Recommendations about GR/Best Practices
- Jakarta: Define tracking process being approved by TSC prior M1

#AGREED the TSC approves the Istanbul release as passing the M4 milestone with the condition that
- The Global requirements tasks status is understood by Sept. 23
- The following Project and Use Case tasks are to be closed by Sept 30: DOC-760 DOC-761 USECASEUI-596 USECASEUI-597 USECASEUI-602 CCSDK-3444 INT-1965 INT-1966 MSB-612 MSB-614 MULTICLOUD-1389 MULTICLOUD-1390 MULTICLOUD-1392 OOM-2807 SDNC-1596 SO-3751 SO-3756 DCAEGEN2-2900 DCAEGEN2-2898 VFC-1877 CPS-606 MSB-610 REQ-914 REQ-902

#AGREED the TSC approves the Istanbul release as passing the M3 milestone with the condition that the following items are to be closed by M4 on 16 Sep 2021 : CCSDK-3355 DMAAP-1633 MSB-608 MULTICLOUD-1368 INT-1937 INT-1935 SDNC-1578 SO-3683 SO-3687 USECASEUI-591 VFC-1874 VNFSDK-791
#AGREED the TSC confirms @Michał Jagiełło as the new Integration PTL
#AGREED the TSC wishes to pursue this agreement \[as captured in the meeting minutes\] with TM Forum
#AGREED TSC approves the Technical Community Document in the form attached hereto as Technical Community Document v2.0.pdf with the above agreed upon change \[of adding "or via the TSC Proxy wiki page." \] to 4.2.1.6.2 as being hereby confirmed, approved, and adopted

#AGREED the TSC approves the OOM Gitlab POC using CLA validation via the ci chain demonstrated in https://gitlab.com/kopasiak/oom_cla_test/-/merge_requests/1 as a workaround until EasyCLA supports GitLab
#AGREED Istanbul M3 slips until Sept. 2nd; discussion with the PTLs on Monday to understand the status and their blockers

#AGREED ESR UI/ESR Server is to be removed from ONAP beginning with Istanbul
#AGREED where the copyright statement names ONAP specifically remove the year.
i.e. for RTD copyright it would read:

#AGREED TSC approves that for Istanbul we maintain the current stability/resiliency acceptance criteria until community members raise an improvement request to be assessed for the next release.
#AGREED since the TSC is approving unmaintained projects in a release the exception filing should be made by the TSC itself. (in reference to AAI-ESR)

#AGREED the TSC approves that Due to the complexity of the OOM project, the ONAP TSC agrees that the OOM project (code & CI jobs) moves under Gitlab as soon as the CLA is approved. If CLA is not approved by Aug 19th then the ONAP TSC will reconvene to assess other options/alternatives to support the OOM project. Currently only the OOM project (all repos) is targeted to move to Giltab

#AGREED extension on exceptions to M2 of one week, due to extended arch review schedule to June 29
#AGREED on pursuing a POC for ScanCode.io - we need to identify where to run the POC.

#AGREED: the TSC approves the SonarCloud profile management model as described in the Proposal
#AGREED that the regular elections of the TSC shall occur annually in September

#AGREED the TSC approves https://lf-onap.atlassian.net/browse/REQ-396 and https://lf-onap.atlassian.net/browse/REQ-399 as TSC best practices for Jakarta
#AGREED TSC moves the VID and ExtAPI projects to Unmaintained status.