Make a release recommendation from a completed evidence packet.
Instruction: Choose a release action, identify what the supplied evidence supports and write explicit operational gates and rollback triggers.
Fictional build A17 adds address suggestions for US/UK customers. Suggestions require customer confirmation; manual entry is available. Product permits an initial 10% cohort for two hours, followed by an expansion decision. The release manager owns activation.
The packet contains: 48/48 acceptance, 12/12 access and 18/18 keyboard/screen-reader cases passing on the supported device matrix; privacy approval for vendor fields and retention; a 30-minute staging test at twice forecast peak within agreed latency/error limits; passing feature-off regression and production-config rollback rehearsal. Flag propagation completed within 60 seconds. On-call and support are staffed. A misaligned icon at 200% zoom has documented Product/accessibility acceptance, with usable controls and a fix owner. No high-impact defects are open.
The runbook requires flag-off for access/privacy violations, loss of manual entry, saved-address corruption, or suggestion errors above 1% in a five-minute window with at least 1,000 requests. Suspected critical events are investigated immediately at any volume. Recommend an action and conditions for changing it.
Updated
Official answer available
Read the opening below, then unlock the full answer and practical guidance.
I recommend activating the approved 10% US/UK cohort on build A17 for two hours. The evidence meets the defined functional, access, accessibility, privacy, performance and rollback gates...
Related Questions
-
easy
-
easy
-
easy
-
easy
-
easy
-
easy