DRAFT PROPOSAL FOR COMMENTS
| Table of Contents | ||
|---|---|---|
|
Overview
...
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 outNIL | NIL |
Known Defects and Issues
Provide a link toward the list of all known project bugs.
...
| Risk identified | Mitigation Plan | Contingency Plan | ||
|---|---|---|---|---|
| To fill out | To fill out | To fill outAAF availability | CLI is depending on the AAF for user authorization as AAF is approved project. In the mean time, it would try to use Portal API for the same. | - |
Resources
Fill out the Resources Committed to the Release centralized page.
...
It is not expected to have a detailed project plan.
| Date | Project | Deliverable | ||
|---|---|---|---|---|
| To fill out | To fill out | To fill outNIL | NIL | NIL |
Documentation, Training
- Highlight the team contributions to the specific document related to he project (Config guide, installation guide...).
- Highlight the 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
- ...
...