Release Lifecycle
Note: This page is out of date. See the current release process description here: https://lf-onap.atlassian.net/wiki/x/7zX7
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.
Definitions
A project is:
- Long term endeavor setup to deliver features across multiple releases
- Single entity solely responsible for one or multiple repositories
- Has a defined scope
- Led by PTL and committers with expertise in the relevant areas
A project is not:
- Release plan
- Collection of unrelated items
- Broadly scoped without clear rationale
- Existing without repo(s)
- Single-release vehicle
- Scoped so broadly to require committers with different expertise
A Release is:
- Short term endeavor setup to deliver a specific Release Use case
- An agreed common framework (template, criteria, best practice) for all projects
- An unique release planning calendar with pre-defined milestones for each project to sync up with
- A vehicle to coordinate multiple projects and multiple type of projects (development, integration, packaging, deployment, documentation, training)
- Led by a Release Manager
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.
|
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 |
|