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


  • Schedule
  • Guilin RC1 / RC2 / Sign Off
    • Seshu reported on Monday that SO / OOM issue has been resolved
      • RC0 exceptions have been closed
    • X-testing on Guilin branch began yesterday (Nov 18)
      • Morgan Richomme notes change in policy for docker hub. No x-testing results for today.
    • Guilin Milestone Status 
    • Issue status (i.e., non-relman)
    • Integration status
    • Release management issues published - 65% completed
      • No update from MSB
        • Morgan Richomme notes that there are no updates to MSB docker from Frankfurt
      • Verify readiness:
        • DMaaP - use RC0 container - to be confirmed with the Project team
        • Waiting OOM: AAI, Policy, OOF, CCSDK
        • Integration Team to confirm all the projects marked as "Delivered"
      • Documentation
        • General RN refer to "Frankfurt" instead of "Guilin"
        • Project Release note not in sync between "Guilin" branch and "latest"
        • Review of Guilin Marketing Message
    • #AGREED BY TSC - Does the TSC agree that the release note will only focus on the Guilin USe Case, Functional and non functional requirements - Guilin Release Requirements + former use cases/functional reqs approved by the Integration Team? If an issue occurred on previous use cases/blue prints/functional reqs then we invite people to open a JIRA ticket against Guilin for assessment? YES
    • Next Steps: RC1/2/Sign-Off Milestone will be reviewed during PTL call (Nov 23rd)
      • Final call to confirm regression use cases/functional requirements as part of Guilin
        • Add Sign off date in the release note: Dec 3rd, 2020
        • Add a note in the release note that AAF, APPC, AAI/ESR, MUSIC, Logging incl. Pomba
        • are in maintenance so information are available in the Frankfurt release note.
        • Reply to Morgan's e-mail - https://lists.onap.org/g/onap-tsc/message/7278 - Final reply not later than Nov 23rd, EOD
        • Confirm final containers (OOM, Integration)
        • Run final gating on the latest containers from Nov 24th until Dec 2nd, 2020
        • Finalize Release Note & Marketing Message
        • Descope, reduce any functional requirement/ non functional requirement not completed by Nov 23rd, 2020
        • Stability Run as soon as Gating are Green.
        • Marketing Launch planned on Dec 10th, 2020
  • Honolulu
    • Schedule proposed but is being actively reworked based on feedback and discussion
    • Results of survey on PTL availability in December
    • Requirements in alignment with the new release cadence process: Honolulu Classification
    • SO team will not work on any Spec, Feature, Use case for the Honolulu release
    • Next Steps:
      • TSC to review best practices and GRs
      • TSC to review/update M1 approval field
      • Requirement Owners to start to socialize their requirements with the project teams who have completed their Guilin activities
Rescheduled on Dec 3rd, 2020

Release Process


Review of schedule for Honolulu using the new release process, including release management requirements for projects at each milestone

View file
namerelease cadence for ptls.pptx
height250

5

RelEng/Infrastructure

  • Tickets- Open showstoppers:
  • Tickets- Waiting on Community:
  • Migration Status / Upcoming Changes

5

PTL Update

Integration

10

TSC Activities and Deadlines

5

Upcoming Events

Linux Foundation
  • No TSC Call on November 26th, 2020
  • Project Maintenance Taskforce discussions will resume on December 1st, 2020 at 2pm UTC
  • LFN Developer & Testing Forum - Feb 1 - 4, 2021.  Proposal and reg page coming soon. 

Action Items

  •  

Zoom Chat Log 

06:06:21 From Olivier PHENIX (Bell Canada) : #info Olivier Phenix, Bell Canada
06:09:23 From Catherine Lefevre : GREAT TEAM Spirit !!!
06:09:56 From Catherine Lefevre : Thanks to all the people who have been helping to solve these issues
06:24:32 From Morgan Richomme : https://docs.onap.org/projects/onap-integration/en/latest/docs_usecases.html#docs-usecases
06:24:47 From Morgan Richomme : https://docs.onap.org/projects/onap-integration/en/frankfurt/docs_usecases.html
06:34:36 From Catherine Lefevre : Does the TSC agree that the release note will only focus on the Guilin USe Case, Functional and non functional requirements - https://lf-onap.atlassian.net/wiki/display/DW/Guilin+Release+Requirements + use cases/functional reqs that have been regression tested and communicated back to Morgan? 
06:35:29 From Catherine Lefevre : If an issue occurred on previous use cases/blue prints/functional reqs then we invite people to open a JIRA ticket against Guilin for assessment
06:35:33 From SaiSeshu MUDIGANTI (Huawei) : Just a suggestion to change it to integration team approval for better understanding of non onap users 
06:36:04 From SaiSeshu MUDIGANTI (Huawei) : Morgan to integration team 
06:36:29 From SaiSeshu MUDIGANTI (Huawei) : @Catherine
06:37:15 From Catherine Lefevre : thanks Seshu - here is another attempt
06:37:19 From Catherine Lefevre : --------------------------------------------------
06:37:22 From Catherine Lefevre : Does the TSC agree that the release note will only focus on the Guilin USe Case, Functional and non functional requirements - https://lf-onap.atlassian.net/wiki/display/DW/Guilin+Release+Requirements + former use cases/functional reqs approved by the Integration Team? 
If an issue occurred on previous use cases/blue prints/functional reqs then we invite people to open a JIRA ticket against Guilin for assessment
06:38:12 From SaiSeshu MUDIGANTI (Huawei) : #vote +1
06:38:58 From Catherine Lefevre : TSC please vote :-) thank you
06:39:03 From Catherine Lefevre : or proxy
06:39:11 From Dong Wang (China Telecom) : #vote +1
06:39:47 From Catherine Lefevre : #vote +1
06:40:03 From Ciaran Johnston (Ericsson) : #vote +1
06:40:09 From Ranny HAIBY (Samsung) : #vote +1
06:40:10 From Olivier PHENIX (Bell Canada) : #vote +1
06:42:21 From Catherine Lefevre : still need additional TSC vote to conclude - thank you
06:43:33 From Alla Goldner : #vote +1
06:45:21 From SaiSeshu MUDIGANTI (Huawei) : Do we have the quorum today? 
06:45:34 From Timo Perala (Nokia) : #vote +1
06:45:35 From Jason Hunt : #vote +1
06:45:51 From Andreas GEISSLER (DT) : #vote +1
06:47:52 From Fernando (Fred) Oliveira : +vote +1
06:48:01 From Fernando (Fred) Oliveira : #vote +1
06:53:01 From Eric Debeau : #vote +1
06:55:24 From bin.yang@windriver.com : #vote +1
06:58:38 From Guangrong FU : That’s what’s confusing me. I’ll make some change regarding the engine module.
06:58:52 From Guangrong FU : Thanks, Andreas.
07:01:27 From Olivier PHENIX (Bell Canada) : I’m sorry, I’ll need to drop, got pulled in for an urgent matter :(
07:01:29 From Xin Miao - 嫩芽 : Have a drop for another internal meeting.  Thanks.
07:01:30 From Olivier PHENIX (Bell Canada) : Apologies
07:09:57 From Jason Hunt : do you need the TSC to attend Monday’s PTL call?