...
| O-DU High | ||
| Criteria | Result / Proof point | |
|---|---|---|
Bug-reporting process | ||
| The project MUST provide a process for users to submit bug reports (e.g., using an issue tracker or a mailing list). (URL required) | Met | Jira : https://jira.o-ran-sc.org/projects/ODUHIGH Mailing list : https://lists.o-ran-sc.org/g/discuss: discuss@lists.o-ran-sc.org |
| The project SHOULD use an issue tracker for tracking individual issues. | Met | Jira : https://jira.o-ran-sc.org/projects/ODUHIGH |
| The project MUST acknowledge a majority of bug reports submitted in the last 2-12 months (inclusive); the response need not include a fix. | Met | |
| The project SHOULD respond to a majority (>50%) of enhancement requests in the last 2-12 months (inclusive). | Met | |
| The project MUST have a publicly available archive for reports and responses for later searching. (URL required) | Met | https://jira.o-ran-sc.org/projects/ODUHIGH/issues/ |
Vulnerability report process | ||
| The project MUST publish the process for reporting vulnerabilities on the project site. (URL required) | UnmetMet | Jira : https://jira.o-ran-sc.org/projects/ODUHIGH |
If private vulnerability reports are supported, the project MUST include how to send the information in a way that is kept private. (URL required) Examples include a private defect report submitted on the web using HTTPS (TLS) or an email encrypted using OpenPGP. If vulnerability reports are always public (so there are never private vulnerability reports), choose "not applicable" (N/A). | UnmetNA | |
The project's initial response time for any vulnerability report received in the last 6 months MUST be less than or equal to 14 days. If there have been no vulnerabilities reported in the last 6 months, choose "not applicable" (N/A). | UnmetNA | |
Quality (13 Points)
(Result/Proof point (column A: enter Met/Unmet; Column B: enter relevant URLs/comments)
...