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

• Eventually, the ClusterExtension API needs to support all content in our existing catalogs as well as bundles that are packaged as helm charts. For the purpose of getting to a 1.0.0 release though, we will start with a subset of that content.

Why is this important?

• …

Scenarios

1. ClusterExtension supports only:

• Registry+v1 bundles
• AllNamespaces mode
• No webhooks
• No dependencies

If criteria not met, OLMv1 will block installation

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. Upstream brief: https://docs.google.com/document/d/1Bwhv00KtFfB5JQ_11JAN00YnyehzGPIyYb3mdnc9GxM/edit 
2. Upstream epic: https://github.com/operator-framework/operator-controller/issues/734 

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>