The content of this template is expected to be fill out for M1 Release Planning Milestone.
...
Refactoring modules
Platform Maturity
No change in the APIs for this release.Please fill out the centralized wiki page: Guilin Release Platform Maturity
Team Internal Milestone (Tentative)
API Incoming Dependencies
List the API this project is expecting from other projects.
Prior to Release Planning review, Team Leads must agreed on the date by which the API will be fully defined. The API Delivery date must not be later than the release API Freeze date.
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.
Third Party Products Dependencies
...
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Please update any risk on the centralized wiki page - Honolulu Risks
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
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: Honolulu Documentation
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.