...
Scope | Priority | Committer Lead | Resources Committed | Epics | Dependencies | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
TSC Must Haves | Highest |
| |||||||||||||||||||
| Policy Lifecycle & Administration API enhancements | High |
| |||||||||||||||||||
Control Loop Sub Committee Functional Requirements | High |
| |||||||||||||||||||
| Cleanup of Policy repos to remove legacy policy/engine and all related code base. | High | All resources are supporting these tasks. |
| ||||||||||||||||||
| Actor model enhancements | Medium |
| |||||||||||||||||||
| Add DMN (Decision Modeling Notation) evaluation support to drools-pdp | Medium | Chris Ramstad & Ciena team |
| ||||||||||||||||||
| Contributions from AT&T | Medium | Bobby Mander & Internal AT&T Policy Team |
| ||||||||||||||||||
| Technical Debt - addressing bugs, leftover work from Frankfurt, code coverage, sonar fixes, etc. | Medium | All resources are supporting these tasks. |
| ||||||||||||||||||
| 5G OOF Use Cases - Control Loop Coordination usage | Medium | Wipro team |
| ||||||||||||||||||
| E2E Network Slicing use case | Medium | Wipro team |
|
...
Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.
...
Indicate where your project fit within the ONAP Architecture diagram.
Block and sequence diagrams showing relation within the project as well as relation with external components are expected.
...
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.
...
Policy R7 Guilin CSIT/External Lab Functional Test Cases
Jorge Hernandez - Committer Lead for all integration Testing and Lab updates.
Gaps
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.
...
Please update any risk on the centralized wiki page - Guilin Risks
Resources
Fill out the Resources Committed to the Release centralized page.
Release Milestone
The milestones are defined at the Release Level and all the supporting project agreed to comply with these dates.
...
It is not expected to have a detailed project plan.
Date | Project | Deliverable | ||
|---|---|---|---|---|
| To fill out | To fill out | To fill out
| 1st Release | All the updated docker images that fixed security issues, dependency upgrades, bug fixes, and sonar cleanup. |
Documentation, Training
Please update the following centralized wiki: Guilin Documentation
...
Each project must edit its project table available at Project FOSS.
Policy FOSS Wiki
Charter Compliance
The project team comply with the ONAP Charter.