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 2 Current »

1 Definitions

TermDefinitionDe
ONAP ReleaseAn ONAP release is the release of a set of artifacts from the ONAP projects that is collectively release together
ONAP project Release

An ONAP project release is a release of artifacts from a specific ONAP project.

Explanatory Note: ONAP projects are listed in the ONAP wiki under approved ONAP projects.  An ONAP project can have releases corresponding to the ONAP releases (e.g. Amsterdam, Beijing).

Latest current releaseRefers to the latest ONAP project release, and in particular to the major revision
 A severe bug An issue that causes the projects deliverables to:
  • Be unstable
  • Not perform the agreed use cases or functionality.
 A high bug

An issue that causes the projects deliverables to:

  • Not perform as expected or described as part of the release.


2 Maintenance Policy

  • An ONAP project is required to perform a maintenance release to support the following:
    • To ensure that there are no known severe or high vulnerabilities greater than 60 days old
    • To ensure that a fix for new severe or high vulnerability is release within 60 days
    • To ensure that severe bugs are fixed within 60 days.
  • The ONAP project applies the patches to the latest current major release (Release N)
    • Note, later upon new TSC decision can be made for the previous major release (Release N-1).
  • The ONAP projects decide whether an issue is a Severe Issue, High Issue or other.
    • •The issue requester, if s/he disagrees with the project decision can request a decision from the TSC by:
      • Sending an email to the TSC with the subject: “Issue Priority Decision Request”
    • Preparing the decision motivation material for part of the TSC agenda.
    • 1 weeks notice is required.
  • Projects can request to the TSC to have a individual project release or a ONAP release.
    • Email to the TSC or request agenda time at a TSC meeting, including testing proposal
  • The TSC will decide to proceed with an individual project release or a overall ONAP release.

• Individual project release criteria:

  • Individual project release activities have been performed
  • Health test and additional testing required by the TSC during release approval.
  • Documentation is updated.

•ONAP project release criteria

  • Individual project release and in addition Regression test of the release use cases performed by the integration team.



  • No labels