OCP/Telco Definition of Done
Epic Template descriptions and documentation.

Epic Goal

• Today the ClusterExension API relies on Rukpak CRDs to be present on the cluster to apply bundle contents to a cluster. The work defined in this epic will replace that use of the BundleDeployment API to instead use Helm as its method of managing content installation to the cluster.

Why is this important?

• …

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. Upstream brief: https://docs.google.com/document/d/1GvmHQxjwCOS6xEZqWTCf5UoQB3DzdSMKIKfJZLiG3X0/edit#heading=h.btd8kkom5km4 
2. Upstream parent issue: https://github.com/operator-framework/operator-controller/issues/733 

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>