Questions about feature launch process

[Eric Huang]

Hi,

I am contributing a CSS feature to Blink, the reviewer requires me to send a Intent to Ship email.

The issue is to support keyword format at @font-face src property: https://bugs.chromium.org/p/chromium/issues/detail?id=1242683

I am not sure if I need to go though those processes defined in Launching Features document before sending the email since it's a small change, or I can directly send the email using email templates.

Many thanks,

Eric Huang

[Daniel Bratell]

Assuming you are talking about the list at https://www.chromium.org/blink/launching-features, the steps for "Implementations of already-defined consensus-based standards", which I think applies here (?), seem reasonable, though you might be able to skim the first steps.

You should use ChromeStatus. It's strongly recommended (possibly even mandated but I'm not 100% sure about this) that developer visible changes get an entry there. It will ensure your change gets much better visibility and ends up in blog posts listing developer visible changes.

For the steps, or fields, which you think do not apply, explain why they do not apply. For instance, requesting signals directly from other vendors would be unnecessary if it's something they implemented long ago.

The reason we do this is to make sure we don't make mistakes that will hurt users, developers, the web platform and the Chromium project. Consider it based on lessons learned.

/Daniel

--
You received this message because you are subscribed to the Google Groups "blink-api-owners-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-api-owners-d...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-api-owners-discuss/CALDfb_orrLAj75sqrmA1ov44WXQLtrSDWG4pNmemMNu-oRLR9g%40mail.gmail.com.