-
Epic
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
CRD Compatibility Checker GA
-
Product / Portfolio Work
-
-
100% To Do, 0% In Progress, 0% Done
-
False
-
-
False
-
Not Selected
-
S
-
None
Epic Goal
Deliver all functionality of the CRD Compatibility Checker required for GA. Specifically, in addition to phase 1 this will include the addition of the Unknown field prevention feature.
Why is this important?
The Unknown field prevention functionality is important to end users and OpenShift engineering as it prevents end users from accidentally creating configurations which could potentially cause unpredictable upgrade behaviour.
Scenarios
From CRD Compatibility Checker use case UC4.
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>
