...
Attendance is taken purely upon #info in Zoom Chat
| AMDOCS |
| | IBM |
| DT |
| | China Mobile |
| WindRiver |
| | Turk Telecom |
| AT&T |
| | Reliance Jio |
| Ericsson |
| | Bell Canada |
| Vodafone |
| | Samsung |
| China Telecom |
| | Huawei |
| Orange |
| |
Yipan
Time (mins) | Agenda Items | Presented By | Presos/Notes/Links/ | JIRA Tasks |
---|
| Welcome Dong Wang |
| Congratulations on being confirmed as the new TSC rep for China 60 |
|
60 | Release Status | | - M4
- Blocking items
- Morgan Richomme notes that not all of the HTTP port issues are documented in JIRA
- Frankfurt Milestone Status
- #AGREED The TSC approves of the following projects for Frankfurt M4: AAI, DCAE, SDNC, VFC, SO, MultiCloud
- Code coverage task moved to Frankfurt RC0 (March 26)
- Additional requirement for Sonar migration
- Requirements
- #AGREED The TSC approves
Jira Legacy |
---|
showSummary | false |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | REQ-140 |
---|
| , Jira Legacy |
---|
showSummary | false |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | REQ-37 |
---|
| , Jira Legacy |
---|
showSummary | false |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | REQ-150 |
---|
| , Jira Legacy |
---|
showSummary | false |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | REQ-84 |
---|
|
Jira Legacy |
---|
showSummary | false |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | REQ-118 |
---|
| , Jira Legacy |
---|
showSummary | false |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | REQ-129 |
---|
| , Jira Legacy |
---|
showSummary | false |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | REQ-76 |
---|
| , Jira Legacy |
---|
showSummary | false |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | REQ-174 |
---|
| , Jira Legacy |
---|
showSummary | false |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | REQ-215 |
---|
| , Jira Legacy |
---|
showSummary | false |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | REQ-219 |
---|
| & Jira Legacy |
---|
showSummary | false |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | REQ-227 |
---|
| as documented in v572 of the Frankfurt Release Requirements
- RC0
| |
5 | RelEng/Infrastructure | | Remember - code coverage criteria i.e. 55% AND migration to SonarCloud must be completed by RC0 |
|
5 | PTL Update |
| - Update on release management task "Address all security issues"
- SECCOM and PTLs agreed on compromise at March 9 PTL meeting
- Best effort on OJSI tickets for Frankfurt, except for
Jira Legacy |
---|
showSummary | false |
---|
server | System Jira |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | REQ-231 |
---|
| - REQ-231 is mandatory with some exceptions
- Projects not participating in Frankfurt
- Projects impacted by AAF
- Non-ONAP components
- Additional exceptions considered on a case-by-case basis
VOTE: Does the TSC approve the changes to the release management task, "address all security issues" as described above? |
|
10 | Subcommittee UpdateArchitecture Rescheduled to 3/19 | | Documentation Prototype review Arch review policy and process VOTE: Does the TSC approve the architectural review policy and process documented above. |
|
30 | El Alto RetrospectiveAction Plan Rescheduled to 3/19 | | El Alto Retrospective Results (move to next week's meeting) |
|
5 | Documentation Hackathon results + Wiki Migration StatusRescheduled to 3/19 | | |
|
5 | TSC Activities and Deadlines | | Review 2020 Mentor Projects TSC Task Force - Cloud Native - Initial Feedback
- Request ONAP Subcommittees to identify 1 representative to join the ONAP CNF Task Force - Please send an e-mail to Kenny and David
|
|
5 | Upcoming Events | | - ONAP Documentation hackathon - March 25th
- Please add your topic to the planning page
- LFN Technical Meetings - Virtual Event
F2F Events (depending on COVID-19 evolution): - LFN Developer and Testing Forum on June 1-4, 2020 - TBD may be a Virtual Event
- ONAP 2 day event after ONS North Europe - Antwerp (TBD)
- Survey will be sent from LFN for Dec OR Jan for steady-state full DDF meetings to all LFN communities & location
| |
...