You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Requirements

  1. All ONAP projects that commit code to a repository are subject to an architectural review.
  2. ONAP projects that do not plan to participate in a release are still subject to architectural review, if they plan to commit code to a repository.
  3. All projects should assume that they require an architectural review.  The decision about whether a review is required will be made by the architectural subcommittee and not by the project.
  4. Projects may choose not to participate in a review. However, the architectural subcommittee will report review status to the TSC, and review participation may influence whether the TSC approves a project to move forward at a milestone.  In addition project review status will be published in the release notes.

Process

  1. Release contents/requirements approved at M1.
  2. Project PTLs have requested a review from the arch subcommittee and have been assigned a JIRA issue. 
    1. The JIRA issue should be documented in the arch review task for the M1 milestone epic for each project.
    2. Projects that are not participating in the release should still request a review if they intent to commit code during the period of the release.
  • No labels