This centralized page, for all Jakarta projects, is aimed at identifying the risks as they are foreseen within the release life cycle.
A Risk that materialized becomes an Issue.
Status:
- Identified: a risk that has been identified, but has not yet been analyzed / assessed yet
- Assessed: an identified risk which currently has no risk response plan
- Planned: an identified risk with a risk response plan
- In-Process: a risk where the risk response is being executed
- Closed: a risk that occurred and is transferred to an issue or the risk was solved/avoided
- Not occurred: a risk that was identified but that did not occur
- Rejected: created and kept for tracking purposes but considered not to be used yet
| Risk ID | Project Team or person identifying the risk | Identification Date | Risk (Description and potential impact) | Team or component impacted by the risk | Mitigation Plan (Action to prevent the risk to materialize) | Contingency Plan - Response Plan (Action in case of the risk materialized) | Probability of occurrence (probability of the risk materialized) High/Medium/Low | Impact High/Medium/Low | Status | Notes |
|---|---|---|---|---|---|---|---|---|---|---|
| 1 | DCAE |
| REQ-438 - COMPLETION OF JAVA LANGUAGE UPDATE (v8 → v11) dcaemod-designtool & dcaemod-nifi-registry has dependency on upstream (NiFI) project which is currently on java8 | DCAE | Continue version | Extend the Waiver/Exception filed for H release | High | Low | Assessed (Discuss with SEECOM on current waiver extension) | |
| 2 | AAI |
| Lack of resources to deliver Jakarta high bugs/issues & global requirements | AAI | Make best efforts to resolve the global requirements and high issues | Raise an exception for this release and make best efforts to resolve | High | Low | ||
| 3 | AAI |
| Janusgraph does not support Java 11
| AAI | Not much we can do repos affected: aai-common, aai-graphadmin, aai-resources, aai-traversal | Raise an exception for this release and hope janusgraph supports java 11 in the coming release | High | Low | ||
| 4 | INTEGRATION |
| Lack of lab resources to run daily/weekly tests Tests are running on the Nokia, Orange and DT labs. If there are some issues or companies plans to withdraw the project we could be out of tests results. Will be best to have lab resources on community labs to run tests on them (independent) | INTEGRATION | Find a lab to run tests on them | Use one of the gating labs or the integration lab to run tests. Queue of the gating tests will be longer and/or the integration lab won't be available | Medium | High | ||
| 5 | OOM |
| Lack of resources on OOM | OOM | have more committers | High | High | |||
| 6 | MULTICLOUD |
| Lack of resource on Multicloud | MULTICLOUD | Make best efforts to resolve the global requirements and high issues | Raise an exception for this release and make best efforts to resolve | High | Low | ||
| 7 | SO |
| Lack of resources to deliver Jakarta high bugs | SO | Make best efforts to resolve | Raise an exception for this release and make best efforts to resolve | High | Low | Assessed and worked upon on priority, remaining items are moved to the next release |
