...
Note: This page is out of date. See the current release process description here: https://wiki.onap.org/x/iECLBQ
The activities of the ONAP community are articulated around Projects and Releases.
The Release Lifecycle should be considered as a sub process of the overarching Project Lifecycle (as defined in ONAP Charter).
The Project Lifecycle should be seen as a long term endeavor (1-2 years) whereas the Release Lifecycle has a short term goal (next 5-6 months).
...
ONAP is adopting a simultaneous delivery model, meaning that all contributing projects have to follow the cadence and intermediate milestones.
The ONAP current release plan is
...
available here.
Tip | ||
---|---|---|
| ||
A project is:
A project is not:
A Release is:
|
Table of Contents
Table of Contents | ||||||
---|---|---|---|---|---|---|
|
Release Lifecycle Overview
ONAP releases are organized through review milestones
...
. For each milestone, every project has to fill out predefined template.
...
Release Kick-Off
Review | Milestone | Description | Activities |
---|---|---|---|
Kick-Off (Open Intent to Participate) | M0 |
|
...
|
...
|
...
|
...
|
...
| To declare its intent to participate within a Release, the team must:
|
...
Once the Release Kick-Off passed, the following activities are performed:
|
...
|
...
|
Release Planning
Review | Milestone | Description | Activities |
---|---|---|---|
Planning | M1 |
|
...
|
...
| To pass Release Planning review, |
...
each PTL must:
|
...
|
...
...
|
...
|
...
|
...
Once the Release Planning passed, the team continues the architecture, coding, testing, documenting in an Agile 2 weeks iteration scrum framework. |
Release Functionality Freeze
Review | Milestone | Description | Activities |
---|---|---|---|
Functionality Freeze | M2 |
|
...
|
...
| To Pass Functionality Freeze, the PTL must:
|
...
|
...
|
...
|
...
After Functionality Freeze is passed, the team focus on:
|
...
|
Release API Freeze
Review | Milestone | Description | Activities |
---|---|---|---|
API Freeze | M3 |
|
...
| Prior to |
...
API review, Project teams must also review APIs |
...
Architecture Sub-committee.
|
...
API Freeze, the PTL must:
|
...
|
...
|
...
|
Release Code Freeze
Review | Milestone | Description | Activities |
---|---|---|---|
Code Freeze | M4 |
|
...
|
...
|
...
| To pass Code Freeze, the PTL must:
|
...
After Code Freeze is passed, the team focus on:
|
...
|
Release Candidate
Review | Milestones | Description | Activities |
---|---|---|---|
Release Candidate | RC0, RC1, RC2 |
|
...
|
...
|
...
|
...
|
...
|
...
| To pass Integration review, the PTL must:
|
...
|
Release Sign-Off
Review | Milestone | Description | Activities |
---|---|---|---|
Sign-Off |
| To pass Release Sign-Off review, the team must:
|
...
|
Release Sub-Components
Some project teams may need to embed within their releases a set of Sub-Components. Sub-Components can be seen as a distinct piece of code that can be easily upgraded independently from the release deliverable. These Sub-Components must be clearly identified at Release Planning.
Release Components and Sub-Components are defined for all ONAP projects in a central place.
Some tailoring may take place to facilitate operation as we do not want to overload TSC voting members for relatively small sub-project updates.
Release Reviews
To avoid too much of formal review, TSC will provide its formal approval for project Kick-Off and Sign-Off only. However, all reviews must be carefully documented in project wiki.
The same principles applies for Release Reviews as for Project Reviews
...
.
Release Tailoring
Depending on the release scope and project state, the Release Kick-Off and Release Planning Reviews may take place at the same time.
Architecture Review may be skipped for testing or documentation project.
Sub-Component Patch: when it is required to deliver a patch to address a critical issue, a simple email notification to TSC and Release Manager is required.