-
Epic
-
Resolution: Unresolved
-
Major
-
None
-
None
-
MAPI/CAPI Feature Parity (AWS) (Tech Preview)
-
False
-
None
-
False
-
Not Selected
-
To Do
-
OCPSTRAT-683 - Migrate MAPI to Cluster API for AWS -Phase 1
-
OCPSTRAT-683Migrate MAPI to Cluster API for AWS -Phase 1
-
63% To Do, 25% In Progress, 13% Done
-
L
OCP/Telco Definition of Done
Epic Template descriptions and documentation.
<--- Cut-n-Paste the entire contents of this description into your new Epic --->
Epic Goal
- To bring MAPI and CAPI to feature parity and unblock conversions between MAPI and CAPI resources
Why is this important?
- Blocks migration to Cluster API
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>
- clones
-
OCPCLOUD-2706 MAPI/CAPI Feature Parity (Core) (Tech Preview)
- In Progress
- is cloned by
-
OCPCLOUD-2813 MAPI/CAPI Feature Parity (AWS) (GA)
- New
- links to