Epic Goal*

EC builds are produced after each sprint during feature development phase. The EC builds will be added to the candidate channels for us to consume.

By consuming EC builds for running OSUS stage environment we want to dogfood it to improve the quality of each and every builds we produce.

Why is this important? (mandatory)

We want to be a position where each and every build we produce should be production quality.

Scenarios (mandatory) 

1. The cluster should run EC builds, fc builds and RC builds. Once the version is released we will move next EC build available.

Dependencies (internal and external) (mandatory)

1. APP-SRE
2. OTA

Contributing Teams(and contacts) (mandatory) 

Our expectation is that teams would modify the list below to fit the epic. Some epics may not need all the default groups but what is included here should accurately reflect who will be involved in delivering the epic.

• Development - OTA, APP-SRE
• Documentation - NA
• QE - NA
• PX - NA
• Others - NA

Done - Checklist (mandatory)

The following points apply to all epics and are what the OpenShift team believes are the minimum set of criteria that epics should meet for us to consider them potentially shippable. We request that epic owners modify this list to reflect the work to be completed in order to produce something that is potentially shippable.

• CI Testing - Tests are merged and completing successfully
• Documentation - Content development is complete.
• QE - Test scenarios are written and executed successfully.
• Technical Enablement - Slides are complete (if requested by PLM)
• Other