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

• Provide a mechanism that allows control of which catalogs are used for resolution
• Provide a mechanism that supports minimal catalog selection

Why is this important?

• Catalogs may contain duplicately-named operators, and an administrator may want to select an operator from a specific catalog (and thus a specific operator)

Scenarios

1. Two catalogs define the same operator, it is undefined how operator-controller will select the bundle from those catalogs.
2. A new catalog may be installed and may now have duplicated names for operators, and this will cause unexpected behavior.

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>