...
3.3.2. Project Lifecycle Overview
3.3.2.1. The project lifecycle provides the freedom for each team to conduct its project according to their needs, culture and work habits. Thus, the project lifecycle is not prescriptive on how each project operates.
...
3.3.2.
...
2.
...
An ONAP release can be composed of 1 to N projects. As such the number of contributing projects to a particular release may vary overtime.
...
3.3.2.
...
3.
...
A release is initiated to deliver a set of project deliverables.
...
3.3.2.
...
4.
...
The project lifecycle process does not impose a duration for the project nor for the release. There is an independent Release Plan document for each release to specify release timelines which includes, but is not limited to the following:
...
3.3.
...
2.
...
5.
...
Release Plan
3.3.72.15.1. Introduction
3.3.72.15.2. Release Deliverables
3.3.72.15.3. Release Milestones
3.3.72.15.4. Expected Dependencies on Other Projects
3.3.72.15.5. Compatibility with Previous Release
3.3.72.15.6. Themes and Priorities
3.3.72.15.7. Other(s)
3.3.72.15.8. Features delivered
3.3.72.15.9. Non-Code Aspects (user docs, examples, tutorials, articles)
3.3.72.15.10. Architectural Issues (if any)
3.3.72.15.11. Security Issues (if any)
3.3.72.15.12. Quality Assurance (test coverage, etcetc)
3.3.72.15.13. End-of-life (API/Features EOLed in Features EOLed in Release)
3.3.72.15.14. Summary of Outstanding Bugs
3.3.72.15.15. Summary of Standards Compliance
3.3.72.15.16. Delta between planned schedule and actual schedule
3.3.
...
2.
...
6.
...
Release Review
The project shall document results of the review in the release notes
3.3.72.26.1. Features delivered
3.3.72.26.2. Non-Code Aspects (user docs, examples, tutorials, articles)
3.3.72.26.3. Architectural Issues (if any)
3.3.72.26.4. Security Issues (if any)
3.3.7.26.5. Quality Assurance (test coverage, etcetc)
3.3.72.26.6. End-of-life (API/Features EOLed in Features EOLed in Release)
3.3.72.26.7. Summary of Outstanding Bugs
3.3.72.26.8. Summary of Standards Compliance
3.3.72.26.9. Delta between planned schedule and actual schedule
3.3.3. Project Lifecycle States and Reviews
ONAP project lifecycle defines six states that each project goes through. The project lifecycle may extend across multiple releases.
3.3.3.1. The procedure of moving from one state to the next one is independent from the release and the pace depends on each individual project.
3.3.3.2. In order to effectively review project progress, fivereviews are build-in within the project lifecycle.
3.3.3.3. The lifecycle of a project is depicted on the following diagram:
...
3.3.4.3. Tailoring practices will be documented as we progress through our releases. The TSC should respond to requests in a timely manner.
3.3.5. Reviews & Metrics Overview
...
These should contain roughly the following sections:
3.3.7.1. Release Plan
3.3.7.1.1. Introduction
...
3.3.7.1.16. Delta between planned schedule and actual schedule
3.3.7.2. Release Review
3.3.7.2.1. Features delivered
...