Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

« Previous Version 17 Next »

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.

Agenda

START RECORDING

Duration

Agenda Item

Requested byNotes / Links
1 hour

Cross-project discussions

Implement Project Self-Release for the Guilin Maintenance

  • Code: Change (bug fix /security/documentation) on both Guilin Branch and 'Master' 
  • RTD (release note): Document change (bug fix /security/documentation) on both Guilin Branch and 'latest' 
  • Deliver container(s) to Integration team (submitting it to OOM) and succesfully passed the gating
  • OOM impact: Increment container version
  • Communication channel to inform the ONAP community: send an e-mail to the onap-tsc distro
  • CI Gating:
    • Morgan Richomme confirm that we have "Gating resources" are available to support Guilin Maintenance and Honolulu (Master)
  • Content:
    • Requirement owners to improve their documentation
    • Bug fixing and Security issues
    • No new requirement - these requirements must follow the Honolulu Release Cadence

Feel free to review the Project Self-Release process and add comment(s)

LF IT Support

Kenny Paul
Testing Environment

Testing Improvement



CSIT Review



ToolChain Improvement



Documentation

Other Improvement suggestion



Subcommittee Updates for PTLs

  • Honolulu Python and Java baseline images are now available
    • Integration/docker/onap-python/master
    • Integration/docker/onap-java11/master

Sharing Best Practices



IF TIME ALLOWS ....
15 minsRelease status

Honolulu Release

  • Honolulu Release Plan
    • M1 Milestone is scheduled on 1/11 
    • M2 (Spec Freeze) Milestone is planned on 1/21
    • M1/M2 JIRA Tasks will be released soon
  • 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
5 minsUpcoming Events


No PTL Call on 12/21 and 12/28

No TSC Call on 12/24 and 12/31

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

10 minsRemaining Action Items



Zoom Chat Log 


Action Items 

  • Type your task here, using "@" to assign to a user and "//" to select a due date
  • No labels