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

• This epic tracks the work needed to move the ClusterImagePolicy API from v1alpha1 to v1 in OCP 4.20. It does not include any new feature requests, which will be tracked by other epics—just the API upgrade process, CI jobs and related tasks.

The workflow to move to GA:

1. v1 types in o/api
2. client-go to generate v1
3. Add v1 manifest to payload and update MCO to v1 APIs
   1. update featuregate to default enabled
   2. add the v1 manifest to the payload
   3. remove the v1alpha1 manifest from the payload
4. Wait 1-2 weeks - feature promotion in o/api
5. And do those all in order. For 3 here, those PRs that need to be simul-merged

Why is this important?

• Moving the ClusterImagePolicy API to a stable version v1 and announcing that OpenShift now supports Sigstore verification are key steps in helping customers strengthen their software supply chain.

Scenarios

1. ...

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. ...

Previous Work (Optional):

1. …

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>