-
Epic
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
Compliance quick wins
-
False
-
False
-
To Do
-
100% To Do, 0% In Progress, 0% Done
-
0
-
0
Epic Goal
- Some features request come from security compliance regulations. Making it easier to meet those regulation checks would help RHCOS & OCP.
Why is this important?
- Customers have to follow regulations and security compliance lists. Making it easier for them to do so helps them.
Scenarios
- ...
Acceptance Criteria
- CI - MUST be running successfully with tests automated
- Release Technical Enablement - Provide necessary release enablement details and documents.
- ...
Dependencies (internal and external)
- ...
Previous Work (Optional):
- …
Open questions::
- …
Done Checklist
- CI - CI is running, tests are automated and merged.
- Release Enablement <link to Feature Enablement Presentation>
- DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
- DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
- DEV - Downstream build attached to advisory: <link to errata>
- QE - Test plans in Polarion: <link or reference to Polarion>
- QE - Automated tests merged: <link or reference to automated tests>
- DOC - Downstream documentation merged: <link to meaningful PR>
