Versions Compared

Key

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

...

As ONAP is very young project with a lot of code coming in every release. That's why for now Even through we are interested in receiving bugs for all ONAP releases that are currently in use, we will develop patches forpatches  ONLY FOR THE LATEST RELEASE and FOR THE MASTER BRANCH (next version under development) .

...

  1. Create ticket with issue description in Vulnerability Reporting Jira Project (VMS members)
  2. Make the ticket publicly visible (VMS members)
  3. Assign the bug to one of VMS members
  4. Perform bug triage and CVE request if necessary (VMS coordinator)
  5. Send email containing triage results to ONAP TSC Chair and LFN representative /TSC should decide who is this contact point/
  6. Rest of standard process should be followed, skipping embargoed disclosure step

...

  1. Make the related ticket publicly visible
  2. If a patch has been already proposed push it immediately to gerrit
  3. Skip embargoed disclosure.
  4. Send email confirming that issue has been leaked to ONAP TSC Chair and LFN representative /TSC should decide who is this contact point/
  5. Rest of standard process should be followed and finished as soon as possible.

...