XML

Word

Printable

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

Epic Goal

The goal of this epic is to define work need to take over oc-mirror from NAPS team to workload team and GA in 4.11
The agreement with NAPS team is they will still do the coding and bug handling though out 4.11 and make OC-mirror GA
The expectation from workload team is to actively involve in oc-mirror activity in 4.11 example build CI , involve workload QA . the idea here is workload team is ready to take over oc-mirror in post GA in 4.11 and NAPS team will be in consulting mode only . Any bugs and request for feature will handle by workload team beyond 4.11

Why is this important?

CI - MUST be running successfully with tests automated
Release Technical Enablement - Provide necessary release enablement details and documents.
...

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>