The content of this template is expected to be fill out for M1 Release Planning Milestone.
...
Support planned requirments
Requirements
Test Automation
...
- Test Automation
CMCC, HuaweiJira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key REQ-337 - CNTP
HuaweiJira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key REQ-339
TSC must have
Requirement | JIRA Story | Commitment | ||||||||
---|---|---|---|---|---|---|---|---|---|---|
REQ-380 |
| Huawei | ||||||||
REQ-361 |
| Huawei | ||||||||
REQ-351 |
| Huawei | ||||||||
REQ-349 |
| Huawei |
Minimum Viable Product
- Add support for discover and auto-register of schema
...
Following sample YAML shows the YAML file used to create the microservice in Open-O using CLI
openo microservice-create
Platform Maturity
Please fill out the centralized wiki page: Guilin Release Platform Maturity
...
Jira Legacy | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
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).
Risks
NO
Resources
Fill out the Resources Committed to the Release centralized page.
Release Milestone
...
Date | Project | Deliverable |
---|---|---|
To fill out | To fill out | To fill out |
Documentation, Training
Please update the following centralized wiki: Frankfurt Documentation
...
- 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
- ...
...