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

• Both cri-o and podman use the same c/image and c/storage libraries, so we want to make sure the versions of podman and cri-o in an OCP release have same/similar versions of the backend libraries.

Why is this important?

• If a new feature requires changes to c/image and registries.conf and/or policy.json files, we need to make sure that podman doesn't break with the new feature when cri-o is up to date and able to use the new feature.
• We also need to solve the problem of supporting fixes to podman as OCP support is 9 months for regular versions and 18 months for EUS versions.

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>