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

• After pivoting to also providing a ClusterExtension API in addition to an Extension API and focusing on the cluster scoped API for 1.0.0, we will take the relevant improvements made to the Extension API in the last few months and port them over to the ClusterExtension API.

Why is this important?

• …

Scenarios

1. Make the updates of various status fields more orthogonal
   • resolution results
   • progressing state
   • status of the currently installed bundle
   • deprecation status of the currently installed bundle and the specified package and channel
2. Removal of deppy due to the lack of a need for a SAT solver.

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 parent issue: https://github.com/operator-framework/operator-controller/issues/747 

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>