Versions Compared

Old Version 3

changes.mady.by.user cl664y@att.com

Saved on

compared with

New Version Current

changes.mady.by.user cl664y@att.com

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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

01

PTL RecordingsZoom Chat Log

Duration 60 minutes

Duration

Agenda Item

Requested byNotes / Links
START RECORDING
10 minsCLA EnforcementKenny Paul
10 minsDublin Release

Former user (Deleted)

cl664y@att.com

Sylvain Desbureaux

Morgan Richomme

  • Release has been signed-off. Thank you for all your great contribution
  • Dublin Release Retrospective
  • Tagging OOM with 4.0.0-ONAP - it has been tagged but will need to re-tagged after updating the documentation & *.yaml file
  • Review/Update your JIRA tickets
  • Pay attention to onap-discuss - People have started to trial the ONAP Dublin release
  • Review of latest OOM Gating results
30min

El Alto plans review

Former user (Deleted)

PTLs to identify their El-Alto JIRA Tickets based on TSC "Must Have" by June 24th, 2019. TSC to review the "El Alto release" content on June 27

Content of El-Alto Early Drop

When PTL is ready then add the JIRA query on the wiki page - Project Status in El-Alto Release

  • status not in (Closed,Done) AND labels = El_Alto_Early_Drop and project ="Sandbox Project" ORDER BY priority DESC
  • No Content defined yet for
25
  • 20 projects

Please note we have already

34

38 Highest/High Bugs

Image Added


Please note

47

46 Documentation Items

Image Added


Full content of El-Alto Release

1717

1802 items where (affectedversion = “El Alto Release” OR fixVersion = "El Alto Release")

Image Added

Action(s):

-Can we close the tickets in "Delivered" State?

-Security status (OSJI ) i.e. Fix Accepted, Not a security Bug, public Disclosure, Confirmed - what's the termination status? How can we move forward?

-Review "Submitted" if the code has been merged then can move them to "Delivered" for testing

-Can we review "Open/In Progress" - have we really the intention to deliver them over the next 2 months+?

Jira Query

status not in (Closed,Done) AND project not in (CI-Management, "Sandbox Project", "ONAP TSC") AND (affectedVersion = "El Alto Release" OR fixVersion = "El Alto Release") ORDER BY priority DESC

5minOJSI Status

Paweł Pawlak

Krzysztof Opasiak

Amy Zwarico

Review progress on OJSI tickets

OJSI Tickets Status


Global-jjb

Jessica Gonzalez

Deadline July 19th global-jjb Migration Tracker

Windriver Lab Capacity update

+ Gating Evolution (question)

Yang Xu

Brian Freeman

Sylvain Desbureaux

Understand the request for resources Sylvain Desbureaux OOM_CD_Gating_ptl.pdf

Need TSC approval - budget available need a specific request

Kenny Paul to get budget from Finance committee

10 minsManagement of mSOfir Sonsino

How can we manage mS code?

Current proposition is to create separated source code repositories

  • Micro-services expected from Amdocs as a repo
  • Request for more repos (one repo per micro service) - more repos = more Jenkins jobs (more resources)
  • Could combine a number micro services into a single repo
    • At a sacrifice of easily tracked version numbers
  • DCAE has a similar situation
    • Had separate repos - changed in Dublin to have sub-projects with in a repo - worked well
    • LF can help with independent versioning

ONAP certification testingcl664y@att.com

ONAP PTL elections

Kenny Paul



Discuss the PTL JIRA restriction request 

Jessica Gonzalez

Summary of issues related to release version / fix version

LFS Staff SurveyKenny Paul https://www.surveymonkey.com/r/PT68D3Q


Zoom Chat Log 
Anchor
chat
chat


Action Items

  •  2019/07/01 01 Krzysztof Kuzmicki Opasiak , Former user (Deleted)  - Review OSJI ticket status in order to remove JIRA status that we should not track i.e. Not a Security Bug, Public Disclosure etc