Adding an "Adoption" Gate to ChromeStatus Shipping Stages

[Jason Robbins]

Hello blink-dev,

We are adding a new "Adoption" gate to the shipping stage of feature entries in ChromeStatus.

This new cross-functional gate is being introduced to improve coordination between feature owners and cross-functional teams responsible for feature adoption, such as release notes and MDN documentation. The goal is to ensure coordination takes place early enough to support accurate and timely developer relations communications, and ultimately to speed adoption of new web platform features.

The "Adoption" gate will be the last cross-functional gate before the "API Owners" gate in the feature shipping stage. 

The gate will be required for all new feature entries and will be backfilled for any existing features slated to ship in or after M150.

Self-certification will be offered to allow feature owners to immediately clear the gate when common conditions are met:

• Feature details (name, summary, milestones) are up-to-date.

• These fields follow the style guidelines shown in field-level help text.

• There are no late changes to those fields, unless the feature owners have coordinated with the Chrome Docs team for announcements.

• An issue is being tracked for the feature's MDN documentation updates.

If not all conditions for self-certification are met, the feature will be sent to the review team with the usual review SLO.

Also, later this year we plan to expand the scope of the Adoption gate to also require that feature owners help draft guidance for LLMs on how to use the feature.

Thanks,
jason!

[Jason Robbins]

On Friday, April 17, 2026 at 9:48:23 AM UTC-7 Jason Robbins wrote:

... 

Also, later this year we plan to expand the scope of the Adoption gate to also require that feature owners help draft guidance for LLMs on how to use the feature.

Here's a quick update to let you all know that that expansion is already happening.  Specifically, we have added an additional self-certification condition about MWG:

• An issue for your feature is being tracked in the Modern Web Guidance tracker, providing information about how your feature impacts guidance for LLMs, or you have left a comment explaining why there is no impact.

This is a very simple tool integration, but an important change to the feature development process in that it embraces the fact that web developers are very likely to adopt new web platform features through AI coding tools. 

Next up, we'll be building more data validation into the Adoption gate to help feature owners finish the shipping process with feature entries that are accurate and up-to-date.

Thanks,

jason!