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

• Improve the day-to-day experience for those working on LVMS
• Make LVMS more accessible and more open for contributions
• Squash technical debt.

Why is this important?

• Migrating LVMS from the ODF team to OpenShift left a number of gaps and wishlist items involving a lot of manual work. To reduce the amount of manual effort, we should prioritize at least some of the stories in this epic over time to make development easier, builds/releases faster, and fill in existing gaps.

Scenarios

1. As an engineer, I need a comprehensive suite of e2e tests that cover the current functionality so that I have confidence in my pull requests.
2. As an engineer, I need an automated build pipeline so that I can produce a build on-demand.
3. As an engineer, I need access to engineering candidate builds so that I can request early testing from QE.
4. etc.

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>