Epic Goal*

• Documentation is updated to change references from "EUS-to-EUS" updates to "Control Plane Only Updates" so that it's clear that you may update across EUS versions without EUS entitlements in 4.16 and later
  • In already GA'd versions which are updated the header should indicate "Previously referred to as EUS to EUS updates"
  • In 4.14 documentation mention that "In 4.16 and later this has been renamed to Control Plane Only Updates"
• Channel automation adds 4.N-2.z to 4.N stable and fast channels once 4.N channels have updates from 4.N-1.z
  • From stable-4.16 and later
• Intention is to enable this across odd versions, ie: 4.15 to 4.17, pending QE capacity agreement
  • If agreed "Control Plane Only Updates" documentation is added to 4.15
• Intention is to enable this across a stride of 3 releases ie: 4.16 to 4.19 and 4.15 to 4.18, pending QE capacity agreement
  • If agreed, update 

Why is this important? (mandatory)

What are the benefits to the customer or Red Hat?   Does it improve security, performance, supportability, etc?  Why is work a priority?

Scenarios (mandatory) 

Provide details for user scenarios including actions to be performed, platform specifications, and user personas.  

Dependencies (internal and external) (mandatory)

What items must be delivered by other teams/groups to enable delivery of this epic. 

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 - 
• Documentation -
• QE - 
• PX - 
• Others -

Acceptance Criteria (optional)

Provide some (testable) examples of how we will know if we have achieved the epic goal.  

Drawbacks or Risk (optional)

Reasons we should consider NOT doing this such as: limited audience for the feature, feature will be superseded by other work that is planned, resulting feature will introduce substantial administrative complexity or user confusion, etc.

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