Combining ring and percentage rollouts
Before we finish this chapter, I want to discuss of using both ring and percentage rollouts as it provides more opportunities for testing and validating the effectiveness of new features. The most common combination of these two strategies is to start with a ring rollout process, where QA engineers or stakeholders can sign off that the feature is in a position to be presented to real customers. Once that happens, the feature can then be targeted at customers using the percentage rollout.
The following screenshot shows how a feature flag could be configured to target specific users within either a QA or Stakeholders segment, while also serving all other customers with a 50/50 chance of having the feature enabled. The two segments would have specific users added to them (likely to be people within the company) rather than targeting the feature based on the customer's attributes: