Uploaded image for project: 'Release Requirements'
  1. Release Requirements
  2. REQ-439

CONTINUATION OF PACKAGES UPGRADES IN DIRECT DEPENDENCIES

XMLWordPrintable

    • Update vulnerable direct dependencies
    • Best Practice (global - all code)
    • 1
    • Not required
    • Original Scope
    • XS
    • GO
    • GO
    • GO

      Description of Use Case / Requirement:

      Each project will update the vulnerable direct dependencies in their code base following the recommendations of SECCOM documented in individual project pages under Honolulu Package Updates in the protected Security Vulnerabilities space.

      Each project should reference their page for the policy description and correlation with ONAP release milestones.

      Submit a LF Ticket for access to the Security Vulnerabilities space.

      Owners (one of these should be the Assignee - use @ notation): zwarico , Pawel_P

       

      Link to HLD/LLD (if any):

       

      Dependency Relationships with Other Projects:

       

      Project Impact (Test Only (TO), Code (C)): C **

       

      Support Status for each Affected Project (Supported (S); Partially Supported (P); Not Supported (N)):

      Note: for any affected projects labeled 'P' or 'N', please document the resulting gaps.

       

      Integration Leads (use @ notation): 

       

      Company Engagement: 

       

       

            zwarico Amy Zwarico
            Pawel_P Paweł Pawlak
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: