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 4
Next »
Requirements
- All ONAP projects that commit code to a repository are subject to an architectural review.
- 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.
- 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.
- 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
- Release contents/requirements approved by TSC at M1.
- Project PTLs must request a review bye email from the chair of the arch subcommittee and receive a JIRA ticket.
- The JIRA issue must be documented in the arch review task for the M1 milestone epic for each project.
- Projects that are not participating in the release should are still required to request a review if they intent to commit code during the period of the release.
- The project PTL must complete two forms and add links to the forms in a comment to the project arch review JIRA ticket:
- Component Architecture Description Form
- Functional Architecture Description Form
- The arch subcommittee schedules a review with the project PTL
- Arch Subcommittee review
- PTL presents the project, including the submitted forms
- The arch subcommittee reviews the changes and asks the PTL questions
- The subcommittee may approve the project at that point, or ask for changes, or additional information