...
Project Name | Enter the name of the project |
---|---|
Target Release Name | Amsterdam |
Project Lifecycle State | Planning |
Participating Company | Amdocs, AT&T |
Scope
What is this release trying to address?
...
API Incoming Dependencies
Not applicable No new API Incoming Dependency for this release.
The previous dependencies i.e.AAI, SDC, (m)SO, Portal remain unchanged.
API Outgoing Dependencies
...
API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
---|---|---|---|---|
CM | Change management | TBD | TBD | TBD |
NB Interface | REST API | TBD | TBD | Link toward the detailed API description |
...
Third Party | Description | Version |
---|---|---|
Docker | Docker container host | Latest one |
MariaDB | SQL DB | 10.1.11 |
Testing and Integration Plans
...
Jira | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
...
Risk identified | Mitigation Plan | Contingency Plan | |||
---|---|---|---|---|---|
None at this time | N/A | N/A | To fill out | To fill out | To fill out |
Resources
Fill out the Resources Committed to the Release centralized page.
Release 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 recommended to provide these agreements and dates in this section.
...