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 6 Current »

We 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

Release Management Task Review


Selecting new ONAP release names (O, P, Q, R)

  • Plan approved by the TSC last week
  • Please nominate additional names through April 13 (please read the nominating guidelines FIRST)


Suggestion from Liam to reduce the PTL meeting time to 60 minutes (currently 90). We will discuss this further at next week's meeting. 

  • David McBride investigate process and requirements for changing the PTL meeting time.  Simple vote by the PTLs? Does the TSC get involved?

LF IT Support

Jessica Gonzalez 

Maven stage and maven docker stage jobs change from daily builds to on-demand 
(With the option of overwrite in case the project needs it)

Jessica will proceed with the change and then update the TSC and the PTLs on the outcome in 2 - 3 weeks.

Testing Environment

Testing Improvement



CSIT Review



ToolChain Improvement



Documentation

Other Improvement suggestion



Subcommittee Updates for PTLs

Chaker Al-Hakim (Arch Subcommittee)

Roadmap for MSB

Sharing Best Practices



IF TIME ALLOWS ....
15 minsRelease status

Bengt and Jessica looking into

Error rendering macro 'jira' : Unable to locate Jira server for this macro. It may be due to Application Link configuration.
.  Possible blocker for London M3 this week.

Jinquan Ni :  are projects required to upgrade to Java 17.  

Answer:  Global requirement REQ-438 requires projects to upgrade to Java 11 for now. However, Pawel notes that, beginning with Montreal, SECCOM will likely ask projects to upgrade to Java 17.

5 minsUpcoming Events



10 minsRemaining Action Items



Zoom Chat Log 

07:36:48     From PaweÅ‚ Pawlak : ISTIO
07:41:45     From Bengt Thuree (LF) : Unable to locate Jira server for this macro. It may be due to Application Link configuration.


  • No labels