Page Comparison

Proposed Changes:

• New 3rd party dependencies, new FOSS (final confirmation)
• License scan issues addressed
• Address all security issues (I’m not opposed to leaving this, but I’m not aware of any security scans on VNFRQTS though.  If something was raised we would certainly address it)
• All high/highest priority jira tickets addressed
• Update Frankfurt Release Platform Maturity, CII badging update - update M4 Result (Doesn’t seem applicable to VNFRQTS)
• Test coverage goals complete (Not applicable)
• No Gerrit requests older than 36 hrs. (Given we are often getting documentation of things in the release, it’s common for us to receive updates up to the RC0 milestone.  I don’t know if there is a large benefit to this milestone or forcing all contributions in by M4 in our case)
• Integration weather board update  (We’re not part of integration testing)
• Update Frankfurt Risks

Any changes or additions?

Review Old JIRA Tickets for Updated Disposition:

Review JIRA Backlog. Participants should be comfortable that they understand the backlog of tasks for our project ( 5 min)

review:  docs.onap.org ( latest)

vnf guidelines open gerritt

vnf requirments open gerritt

vnf test open gerrit

vnf use cases open gerritt

vnfrqts bugs

Develop Next Sprint Participants should be comfortable with an achievable development sprint scope ( 30 min)

Walk through the JIRA backlog

review handoffs with

DOCS

VVP

VNF SDK

Modelling

LFN C&V

others?

Release Planning:

Frankfurt (new features)

M1 : 11/7/19

M2/3: 1/9/20 - Closed

Frankfurt Epics