Goal

• All Hypershift enhancements, bug fixes and new feature development specific to IBM Power.

Why is this important?

• To synchronise Hypershift with Power.

Acceptance Criteria

• Dev - Has a valid enhancement if necessary
• CI - MUST be running successfully with tests automated
• QE - covered in Polarion test plan and tests implemented
• Release Technical Enablement - Must have TE slides
• ...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. https://issues.redhat.com/browse/MULTIARCH-3434
2. https://issues.redhat.com/browse/MULTIARCH-4666

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Technical Enablement <link to Feature Enablement Presentation>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Enhancement merged: <link to meaningful PR or GitHub Issue>
• 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>