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.
...
| AMDOCS |
| | IBM |
| DT |
| | China Mobile |
| WindRiver |
| | Turk Telecom |
| AT&T |
| | Reliance Jio |
| Ericsson |
| | Bell Canada |
| Vodafone |
| | Samsung |
| China Telecom |
| | Huawei |
| Orange |
| | Intel |
| Verizon |
| | Nokia |
...
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 - 63% 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.
- Need to check final December date for Marketing Launch planned on Dec 10th, 2020
|
| if time allows | Release Process | | Review of schedule for Honolulu using the new release process, including release management requirements for projects at each milestone | View file |
|---|
| name | release cadence for ptls.pptx |
|---|
| height | 250 |
|---|
|
|
5 | RelEng/Infrastructure | | - Tickets- Open showstoppers:
- Tickets- Waiting on Community:
- Migration Status / Upcoming Changes
|
5 | PTL UpdateIntegration | | |
10 | TSC Activities and Deadlines | | - "Project State: Maintenance" Task Force
- "ONAP for Enterprise" Task Force
- Complete the Guilin Release
- Result of CNF poll: Every Thursday after TSC i.e. 3.30pm UTC
|
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.
|
...