January
- #AGREED Jakarta schedule for M4 is to be shifted to March 31st.
- Via Opavote:
- ONAP can have an alternative model to ETSI's approach for our Cloud Native Architecture
- ONAP will proceed without waiting for ETSI to fully define their Cloud Native model
- The current ASD information Model (version 1) will be moved to the “CLEAN State”
- TSC 2022-03-17 #AGREED AAI-3448 is added to the list of jiras that must be resolved by Jakarta M4.
Does the TSC approve Jakarta M3 under the condition that the following issues are resolved by Jakarta M4: INT-2063, OPTFRA-1034. HOLMES-518, MULTICLOUD-1443, SDNC-1661, CCSDK-3585
VFC-1924, DMAAP-1712, OPTFRA-1031 https://lists.onap.org/g/onap-tsc-vote/topic/89687896#1968
- #AGREED Jakarta release milestones will be shifted by one week with signoff on May 12, 2022
- #AGREED the TSC approves the exception request submitted by the Holmes project for Jakarta (https://lists.onap.org/g/onap-tsc/message/8469).
- #AGREED DMaaP is granted a waiver for Jakarta based upon included packages noted on https://wiki.onap.org/x/F4wEBw
- #AGREED TSC approves the M2 milestone for Jakarta with the exception that MULTICLOUD-1431, SDNC-1648, CCSDK-3552, CCSDK-3547, CCSDK-3551 & MULTICLOUD-1429 are closed by the M3 milestone.
- #AGREED Kenny Paul will work on the badging program criteria and then bring the criteria back to the TSC for ratification.
- #AGREED leave Vice Chair vacant in 2022 due to the lack of any self-nomination. If someone shows interest at a later date, we will revisit it then.
- #AGREED the M2 milestone for Jakarta will be shifted to