| Table of Contents | ||
|---|---|---|
|
Overview
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | HonoluluIstanbul |
| Project Lifecycle State | Mature |
| Participating Company | China Mobile, ZTE, Huawei |
...
What is this release trying to address?
etsicatalog project:
- Enhance function of Subscription and Notification for NSD packages
- Support upload Container Images to CIRSatisfy TSC must have items ( stretched goal, depending on the requirement )
- Support Global Requirements
Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key MODELING-461523
Modelspec for modleing subcommittee:
- Create UML models for new model proposals or enhancements in Honolulu Istanbul release
- Document approved models as model specs
...
Modeling/etsicatalog will contribute to the following functional requirements:
Functional requirements:
- R9 ETSI-Alignment Support for Honolulu
Use Case (this Use case has been moved to Jakarta)Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key REQ-400
modelspec will address the following modeling requirements:
Minimum Viable Product
Describe the MVP for this release.
1) ETSI Interface alignment(SOL005 and SOL003) API implement
2) Code contribution to support the ETSI-Alignment Support for Honolulu3) Modelspec from modeling subcommittee
...
Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project=Modeling and issuetype in (epic) and fixVersion="Honolulu Istanbul Release" serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
...
Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project=Modeling and issuetype in (story) and fixVersion="Honolulu Istanbul Release" serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
...
Please fill out the centralized wiki page:Honolulu Istanbul Release Platform Maturity
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.
...
Please update any risk on the centralized wiki page -Honolulu Istanbul 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:modeling
...
The milestones are defined at the Release Planning: HonoluluIstanbul and all the supporting project agreed to comply with these dates.
...
Please update the following centralized wiki:Honolulu Istanbul 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
- ...
...