...
Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project = POLICY AND fixVersion = "Istanbul Release" and resolution != "Won't Do" and issuetype in (epic) 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 = POLICY AND fixVersion = "Istanbul Release" and resolution != "Won't Do" and issuetype in (story) serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
...
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.
...
The testing and integration activities are described in the following page: Policy R9 Istanbul CSIT/External Lab Functional Test Cases
Gaps
No gaps identified.
This section is used to document a limitation on a functionality or platform support. We are currently aware of this limitation and it will be delivered in a future Release.
List identified release gaps (if any), and its impact.
| Gaps identified | Impact |
|---|---|
| To fill out | To fill out |
Known Defects and Issues
Please refer to Frankfurt Defect StatusThere are no major known defects or issues.
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).
Please update any risk on the centralized wiki page - Frankfurt Risks
Resources
Fill out the Resources Committed to the Release centralized page.There are no known risks.
Resources
Please refer to the INFO.yaml for each policy repo:
https://git.onap.org/policy/apex-pdp/tree/INFO.yaml
https://git.onap.org/policy/api/tree/INFO.yaml
https://git.onap.org/policy/clamp/tree/INFO.yaml
https://git.onap.org/policy/common/tree/INFO.yaml
https://git.onap.org/policy/distribution/tree/INFO.yaml
https://git.onap.org/policy/docker/tree/INFO.yaml
https://git.onap.org/policy/drools-applications/tree/INFO.yaml
https://git.onap.org/policy/drools-pdp/tree/INFO.yaml
https://git.onap.org/policy/gui/tree/INFO.yaml
https://git.onap.org/policy/models/tree/INFO.yaml
https://git.onap.org/policy/parent/tree/INFO.yaml
https://git.onap.org/policy/pap/tree/INFO.yaml
https://git.onap.org/policy/xacml-pdp/tree/INFO.yaml
Release Milestone
The milestones are defined at the Release Level and all the supporting project projects agreed to comply with these dates.
Team Internal Milestone
...
It is not expected to have a detailed project plan.
...
...
Documentation, Training
Please update the following centralized wiki: Frankfurt 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
- ...
...
| title | Note |
|---|
...
Minor updates are expected as documented in the Istanbul Documentation
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.N/A
Free and Open Source Software
...