After a new 4.y GAs, we cook for several weeks, waiting to see if any serious bugs turn up before adding the 4.(y-1) > 4.y recommendations to stable-4.y and eus-4.y channels.  This delay can be confusing.  There has been some discussion about using phased rollouts (OTA-191, currently unscheduled) and conditional updates (OTA-267, shipped with 4.10) to make the behavior more discoverable.  But OTA-191 is a big chunk to bite off.  This bug is about whether we want to work up something in the middle to use 4.10's conditional updates to get this information out to folks wondering about stable-4.11 for their 4.10.z cluster, etc.  The message would be something like:

There are supported updates from 4.10 to 4.11 in fast-4.11.  Red Hat is currently collecting feedback about the stability of the release before recommending them in stable-4.11 (or eus-4.12).  We expect to have collected sufficient feedback between $DATE_A and $DATE_B, after which there will either be recommended updates between 4.10 and 4.11 in this channel, or more specific conditional updates mentioning discovered issues.

Definition of done for this spike is:

• Do we agree we want to do this? And:
• Have we created Cincinnati and/or graph-data tickets to track the work we need to implement it?