The content of this template is expected to be fill out for M1 Release Planning Milestone.
...
Functional Requirements :
...
| SO Epic(s) / Story(ies) | M1 Scope and clarification | Java 11 upgrade | Java 11 upgrade to be supported by||||||||||
| Java 11 and Python 3 upgrade of all the SO components, trace elements scanned by Security subcommittee needs to be checked | Python 3trace elements scanned by Security subcommittee needs to be checked |
18 Non functionals :
10 - TSC MUST HAVE (please indicate where you plan to contribute)
...
1 - TSC PRIORITY 2 Continuity (please indicate where you plan to contribute)
7- TSC PRIORITY 3 PTL GO/NO GO (please indicate where you plan to contribute)Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery key in (SO-3493,SO-3473,SO-3459,SO-2695,SO-2427) serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
SO Backlog Overview - Not committed for the release (except for stories that have been captured in the above table), best effort
...
High level architecture diagram
Refactoring modules
Platform Maturity
Please fill out the centralized wiki page: Guilin Release Platform Maturity
Team Internal Milestone (Tentative)
...
...
API Incoming Dependencies
...
Prior to the delivery date, it is a good practice to organize an API review with the API consumers.
...
.
...
API Outgoing Dependencies
API this project is delivering to other projects.
...
No change in the APIs for this release.
Third Party Products Dependencies
Third Party Products mean products that are mandatory to provide services for your components. Development of new functionality in third party product may or not be expected.
List the Third Party Products (OpenStack, ODL, RabbitMQ, ElasticSearchElastic Search, Crystal Reports, ...).
| Name | Description | Version |
|---|
In case there are specific dependencies (Centos 7 vs Ubuntu 16. Etc.) list them as well.
...
| Camunda | Dependency on the camunda engine for processing the workflows |
| MariaDb | Used for all the dependencies on the persistency. |
Testing and Integration Plans
...
Known Defects and Issues
Please refer to Frankfurt Defect Status release notes of Guilin release – To be updated when avail
Risks
List the risks identified for this release along with the plan to prevent the risk to occur (mitigation) and the plan of action in the case the risk would materialized (contingency).
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Please update any risk on the centralized wiki page -
...
Resources
...
Please see the INFO.yaml files associated with each repo as the authoritative sources of information - https://gerrit.onap.org/r/admin/repos/q/filter:so
Release Milestone
The milestones are defined at the Release
...
Planning: Honolulu and all the supporting project agreed to comply with these dates.
Team Internal Milestone
...
This section is optional and may be used to document internal milestones within a project team or multiple project teams. For instance, in the case the team has made agreement with other team to deliver some artifacts on a certain date that are not in the release milestone, it is erecommended to provide these agreements and dates in this section.
It is not expected to have a detailed project plan.
...
Milestone | Description | Date | Comments |
|---|---|---|---|
| M2 | Spec Freeze |
| |
| M3 | Feature Freeze | ||
|
| Last day to submit Honolulu code changes to Gerrit | |
|
|
| |
|
| ||
|
| ||
| | ||
| RC0 | Release Candidate 0 | ||
|
| Last date to submit code fixes for Honolulu RC0 | |
|
| ||
|
| ||
| | ||
| RC1 | Release Candidate 1 | ||
|
| Last date to submit code fixes for Honolulu RC1 | |
|
| ||
|
| ||
|
| ||
| RC2 | Release Candidate 2 | ||
|
| Last date to submit code fixes for final Honolulu release (RC2) | |
|
| ||
|
| ||
| | ||
| Release Sign-Off | Final TSC Sign-Off | | Honolulu Release Sign-Off |
Documentation, Training
Please update the following centralized wiki:
...
That includes
- Team contributions to the specific document related to he project (Config guide, installation guide...).
- Team contributions to the overall Release Documentation and training asset
- High level list of documentation, training and tutorials necessary to understand the release capabilities, configuration and operation.
- Documentation includes items such as:
- Installation instructions
- Configuration instructions
- Developer guide
- End User guide
- Admin guide
- ...
...
...
Note
The Documentation project will provide the Documentation Tool Chain to edit, configure, store and publish all Documentation asset.
Other Information
Vendor Neutral
If this project is coming from an existing proprietary codebase, ensure that all proprietary trademarks, logos, product names, etc. have been removed. All ONAP deliverables must comply with this rule and be agnostic of any proprietary symbols.
Free and Open Source Software
FOSS activities are critical to the delivery of the whole ONAP initiative. The information may not be fully available at Release Planning, however to avoid late refactoring, it is critical to accomplish this task as early as possible.
List all third party Free and Open Source Software used within the release and provide License type (BSD, MIT, Apache, GNU GPL,... ).
In the case non Apache License are found inform immediately the TSC and the Release Manager and document your reasoning on why you believe we can use a non Apache version 2 license.
Each project must edit its project table available at Project FOSS.
Charter Compliance
The project team comply with the ONAP Charter.