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

• To setup CPaaS pipeline for OSUS release branch. This branch will be independent of OCP release branches . 
• To setup a CPaaS pipeline for OSUS master branch. This branch will be setup only to do respective builds in Brew. So that QE can test master branch before we cherry pick fixes to release branch. We do not need to set-up errata for this as we wont release images from this branch. 

Why is this important?

• Setting up new CPaaS pipeline for a new OCP branch is a very time consuming process. Also we only release/maintain one version of OSUS version at any point of time i.e. we do not release mutiple versions of OSUS for each supported minor versions of OCP. The delivery repo (Comet repository) is setup for single stream releases.  So it makes sense  to maintain a single release branch for OSUS as it will make the release process relatively easier.

Scenarios

• With this model, we can have x.y.z as our current release. We build a new x.(y+1).0 adding a new feature. It will go out to the entire OCP fleet as the only version that customers can install or update to. If it is buggy, we will hurry to cut x.(y+1).1, etc. There will be no way to update within x.y.z without opting into the new x.(y+1) features.

Acceptance Criteria

•  New OSUS releases no longer require new OSUS branches.

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>