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! -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/81bf8322-f667-40ac-8966-f1d826008b5cn%40chromium.org.
