| Name | |
| Milestone or Requirements Exception? | Milestone |
Project or Requirement Name and JIRA | SDC |
| Milestones affected | M3, RCX |
| Projects affected | SDC - No other projects affected |
| Background description | SDC had 2 open high OJSI tickets (OJSI-90 and OJSI-94) One ticket was fixed in H release (OJSI-90) but OJSI-94 requires more work. We propose to defer the remaining ticket to the next release as we don't have the resources to fix this issue, current investigations have been shared with the community. |
| Schedule impact | This does not break SDC functionality so we believe this has no impact on schedule |
| Recovery plan | This will be put on the priority list for I release |
| Milestone schedule change | No schedule change, move this to next release |
| Risk | SDC stays vulnerable until fixed, same situation as previous releases, note that H release fixes the main vulnerability on the SDC backend so the situation has improved. |
| Status | Closed |
| Decision | Approved |
1 Comment
Paweł Pawlak
Based on above feedback SECCOM recommends TSC to approve the exception based on the SDC project commitment to continue their effort in fixing remaining OJSI-94 in Instanbul release.