This change should drastically reduce the cases where features must go through the Google internal launch processes before they can ship, and it should also make it clear to Google internal and external contributors when the Google internal launch process is necessary (rarely) and when it is not (most of the time). Approvals should be requested as soon as there’s enough information for the approvers to review (err on the side of early if unsure), and as usual, start the Intent-to-* steps and email blink-dev as soon as you’re ready and API Owners will help make sure the relevant approvals are in place, as they’ve always done. This will help us all make more informed decisions, improve transparency with all contributors and web developers, and launch features more seamlessly.
The
user guide will help you navigate through the ChromeStatus for the various intent processes. And please note that this work is still very fresh and we’re still ironing out some details as we learn more. If you bump into any rough edges or have feature requests, please file a ticket
here.
Thank you to everyone who has worked on this project!
- jstenback (he/him)