OCP/Telco Definition of Done
Epic Template descriptions and documentation.
ACM-wide Product Requirements (Top-level Epics).

<--- Cut-n-Paste the entire contents of this description into your new Epic --->

Epic Goal

• We need to find a way to store the History of Compliance-Events.  One approach is to look into the Common-Compliance-Module but we also would like to have our own approach. The idea is to store the Compliance-Events in Postgresql.

Why is this important?

• Customer demand

Scenarios

1. Customer can configure that he can store the events for the last months

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>