You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 90 Next »

January

1/3 TSC Call

  • TSC agrees to defer any VNF Certification discussion to the VNFRQTS Project.


1/10 TSC Call

  • TSC only approves the CDI projet as POC for the Dublin Release, under the Multicloud project umbrella
  • TSC approves the Committer promotion (AAF): Sai Gandham


1/16

1/17 TSC Call

  • TSC approves the proposed M1 Security milestone checklist as presented by Amy Zwarico. oParent checklist is informational for the Dublin release.
  • TSC approves DataLake  projet as POC only for the Dublin Release under DCAE project umbrella


1/24 TSC Call


1/29


1/31 TSC Call

  • The Casablanca Maintenance Release has been signed-off on 1/31.
  • TSC approves the Dublin Release Plan (M1) for all the projects. Documentation/Integration are conditionally passed.
  • TSC approves v207 of the Dublin Release Requirements GREEN M1 scorecard items and conditional passed on YELLOW items. RED items will be descoped or move to POC depending on feedback collected on 1/31

February

2/4


2/13


2/21 TSC Call

  • TSC did not approve M2/M3 Modeling Checklist add-ons for the Dublin Release. Follow-up discussions with PTLs are required to consider them as part of El-alto release. Suggestion is to prototype these checklists with few projects.
  • Mariusz Wagner committer’s promotion has been approved by the TSC.


2/28 TSC Call

  • Dublin Functionality Freeze (M2) has been approved by the TSC
  • Integration Checklist has been approved by the TSC
  • Multi-VIM/Multi-Cloud Project Scope change has been approved by the Architecture subcommittee - https://lists.onap.org/g/onap-tsc-vote/message/834

March

3/4:


3/7 TSC Call

  • 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


3/21 TSC Call

  • TSC approves moving the M4 milestone to April 11

  • TSC agrees only individual project releases of certificates and critical security fixes in 3.0.2 with impacted area testing only

  • TSC agrees that Deng Hui should continue to be our SDO external coordinator until a new structure/election will occur


3/28 TSC Call

  • 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

4/11 TSC Call

  • TSC agrees the ONAP Release Manager recommendations about M4 i.e. NO-GO, to be reviewed on 4/18


4/18 TSC Call

  • 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.


4/26

May

June

July


In progress

  • No labels