Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


We will start our meetings by mentioning the project's Antitrust Policy, which you can find linked from the LF and project websites. The policy is important where multiple companies, including potential industry competitors, are participating in meetings. Please review and if you have any questions, please contact your company legal counsel. Members of the LF may contact Andrew Updegrove at the firm Gesmer Updegrove LLP, which provides legal counsel to the LF.

Table of Contents
maxLevel1

...

Time
(mins)

Agenda Items

Presented By

Presos/Notes/Links/

45

Release Status

Guilin Maintenance Release:

  • Project Self-Release (Wiki) reviewed with the PTLs on 12/14
  • Content:
    • Requirement owners to improve their documentation about their use cases, functional and non-functional reqs
    • Bug fixing and Security issues
    • No new requirement - any new requirement must follow the new Release Cadence

Andreas Geißler proposes that release notes should include listing  of new features and use cases, with links to documentation updates.  

Andreas Geißlerasks about a completion date for the maintenance release.  Currently there is none.  Let's review again with Catherine and discuss at the next TSC meeting.

  •  Alla.Goldner for Jan 4 Requirements meeting, remind Guilin owners to complete documentation of requirements and use cases for Guilin maintenance release.  Also, discuss linking of features and use cases in the release notes to the related components, per Andreas' suggestion. Also let members know that release management tasks will be added to the REQ epics for every release milestone, beginning with M1 on Jan 11  

Honolulu Release

  • Honolulu Release Plan
    • M1 Milestone is scheduled on 1/11 
    • M2 (Spec Freeze) Milestone is planned on 1/21
    • M2 JIRA Tasks will be released soon
    • Requirement Owners will also be tracked
  • Honolulu Requirement Candidates
    • TSC approved REQ-437, REQ-438, REQ-439, REQ-442, REQ-443 as best practices

    • Projects not participating to Honolulu - It means containers from previous ONAP releases will be used
    • Reminder to approved Best Practice owners to socialize with PTLs and seek approval from TSC nlt M1, if wanting Global Requirement status

5

RelEng/Infrastructure

View file
nameR-and-R Deprecation.pdf
height250

#AGREED proceed with deprecation of R&R page as presented, leaving the current page in place with new pointers to the proper resources.

5

Subcommittee Update

Arch, Ctrl-Loop, Modeling, Seccom, Requirement


Modeling Co-chairs confirmed: Hui DengAndy Mayer

Seccom confirmed: Chair - Paweł Pawlak; Vice-Chair- Amy Zwarico

Control Loop, Architecture and Requirements Subcommittee elections planned early January 2021

5

Upcoming Events

Linux Foundation

No TSC Call on 12/24 and 12/31

No PTL Call on 12/21 and 12/28

LFN Developer & Testing Forum - Feb 1 - 4, 2021.

...