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

• The goal of this epic is to prepare LVMS for maintenance mode. This involves enhancing the stability of LVMS and making it ready for maintenance efforts by increasing its resiliency, ensuring a smoother experience for both developers and end-users.

Why is this important?

• To improve the overall stability and reliability of LVMS.
• To create a more controlled and structured environment for addressing and fixing bugs and issues, especially caused by TopoLVM rebases.

Scenarios

1. An unexpected issue arises within LVMS, impacting its functionality and stability.
2. An unexpected issue arises from a TopoLVM rebase and it is realized only after the rebase is complete.

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. https://issues.redhat.com/browse/OCPEDGE-157 depends on https://issues.redhat.com/browse/USHIFT-599. 

Previous Work (Optional):

1. M&D efforts in v4.14: https://issues.redhat.com/browse/OCPVE-282 
2. M&D efforts in v4.15: https://issues.redhat.com/browse/OCPVE-586 
3. M&D efforts in v4.16: https://issues.redhat.com/browse/OCPEDGE-60 
4. M&D efforts in v4.17: https://issues.redhat.com/browse/OCPEDGE-787

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>