Epic Goal

• Address important SPO issues after the initial release. Make SPO more stable, perform and scale better.

Why is this important?

• Since we're not bound to OCP's schedule, we can make a follow up SPO update and ship a more stable SPO version after the initial SPO release

Scenarios

1. As an SPO user, I want to record a security profile and use it without stumbling upon bugs

Acceptance Criteria

• High priority bugs are addressed
• ...

Dependencies (internal and external)

1. CMP-1091 must be addressed first

Previous Work (Optional):

• SPO must be installable in OCP

Open questions::

1. …

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>