Epic Goal

• fix issues that we haven't gotten to for the first release bug that might be affecting users or SPO stability

Why is this important?

• Even though the first release might have a rough edge here and there, we should make sure that those are addressed
• Similarly, any issues with the build pipeline that might increase the maintenance cost should be addressed

Scenarios

1. As an SPO user, I want my user experience to be smooth
2. As the SPO maintainer I want to produce builds with high confidence and the lowest possible amount of manual work

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

Dependencies (internal and external)

1. SPO GA-ed

Previous Work (Optional):

1. CMP-1091

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>