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 10 Next »

zoom bridge: https://zoom.us/j/283628617

Duration 60 minutes

DurationAgenda ItemRequested byNotes / Links
START RECORDING
5minCasablanca maintenance release status

#1 (Yang): Update the Manifest on Readthedoc

#2 (Mike): Tag the release and will add the version in Helm Chart.

Expected sign-off: 2019-04-25

15min

Dublin end game plans

Former user (Deleted)

RC0 date - 2019-05-02

RC0 templates due - 2019-04-30

  • RC0 milestone checklist
  • No "Submitted" state Jira stories related to code development
  • Complete pair-wise testing weather board and create your individual project pair-wise testing page
  • Integration team to flag failing OOM healthcheck/container restart/pair-wise test for review in weather board
  • Expectation of closed out jiras for Documentation 

Yellow status Release Requirements - move to POC by 2019-04-22 COB

Critical defects - please stay on top of the merges

?Community does not get a chance to give feedback in late cycle - basically insuring a maintenance release immediately following the Sign-Off. Would like 2 wks from RC2 to sign-off/GA?

10min

Dublin Vulnerability review - SECCOM

Projects not yet reviewed

Using Jira tickets for vulnerabilities that need attention. Tracking the release wide vulnerability table review process here: /wiki/spaces/SV/pages/16090768
5minNexusIQ demoPaweł Pawlak

Offline meeting recording: NEXUS-IQ tutorial 17042019.mp4

If you need more help reach out to Amy Zwarico

10minLicense scans review - WinslowSteve Winslow
 <DOWNLOAD the spreadsheet - preview in wiki doesn't work as well>

Process: 

Prior to release the TSC legal subcommittee reviews and approves any license exceptions in dependencies. Steve has reached out to the projects that are using licenses that are not generally accepted. Reach out to swinslow@linuxfoundation.org 

What about binary files in the repo?

Generally not desired - especially a compiled binary as license terms can be obfuscated.

CSAR files for testing? Inside the files there are "proprietary notices" - that's what raises flags.

Zoom Chat Log


Action Items

  • What is the plan for the June ONAP Developers Forum - dates/location/etc  Kenny Paul
    <includes outreach to education - looking at universities>
    <Virtual meeting? - still under investigation>
  • Helm Chart Transfer: 4 projects have been identified for trial: A&AI, Log, Policy, APPC, CLAMP and ONAP CLI. Mike Elliott will work with PTL to gather/transfer knowledge and create training materials. Training to be done the week of Jan 14 and PTL to provide their commitment or not by M1 on Jan 24.
    <1-7/2019>: Work in progress. Schedule might shift to another week. Michael will follow-up with Mike. Training will be open to everybody. The objective is that each team will take over the management of their Helm Charts. 
    <1-28/2019>: Meeting is organized on 1/29 with LF. Training will be organized early in February. Additional information on the next PTL call (2/4)
    <2019-2-19: Meeting on this topic today - review the process - develop training material. OOM subcharts complete - A&AI this week>
    <2019-03-04: Ready to do the first project A&AI; after testing on the first project make video on process flow, several others will follow Jessica Gonzalez Mike Elliott>
    <still working out the A&AI details - in progress; once the POC is complete the other repos will follow>
    <2019-04-08: LF releng - Pushed a patch to a code transfer (test) branch to test out an approach and testing verify job. Once proved out need to work with down stream CI/CD before wholesale push. ><2019-04-22: Ready to start on A&AI -will kick off today!>
  • AAF calling conventions - followup Jonathan Gathman
  •  


  • No labels