FYI, the API Owners unintentionally left out the OT requirement of having some version of a draft spec associated with an incubation group such as WICG, or an existing standards venue. This was discussed in https://groups.google.com/a/chromium.org/g/blink-api-owners-discuss/c/Jzij3fKN5kA/m/I6nqUxUZBwAJ, and documented <https://source.chromium.org/chromium/_/chromium/website.git/+/b2a25f95f9221247bccf291264df7b0f5d9a4ca6> . thanks, Mike On Tuesday, April 19, 2022 at 4:32:46 AM UTC-4 tste...@google.com wrote:
> Reflected this change regarding gapless shipping in our developer-facing > docs (PR <https://github.com/GoogleChrome/developer.chrome.com/pull/2627> > ). > > On Mon, Apr 18, 2022 at 6:22 PM Chris Harrelson <chris...@chromium.org> > wrote: > >> Hi blink-dev, >> >> The Blink API owners have enacted the following changes to the process: >> >> * *Clarification of the number of milestones allowed for an Origin >> Trial, with provision for extensions*. Origin Trials may run for up to 6 >> milestones with today's rules, and may be extended for up to 3 milestones >> at a time if substantial progress is made towards meeting the bar for an >> Intent to Ship. (Extensions still only require one LGTM.) >> >> ** Gapless shipping for all Origin Trials*. When a feature receives >> approval to ship, a breaking period for any existing Origin Trial is no >> longer required. (In other words, all features are automatically allowed to >> ship in a "gapless" way.) This policy will be in place for 12 months, after >> which the API owners will re-evaluate whether it introduces any new risks >> in practice. >> >> See here >> <https://www.chromium.org/blink/launching-features/#step-3-optional-origin-trial> >> for >> more details on the changes to Origin Trials. >> >> * *New Interop question*. There is a new question during the Intent to >> Ship phase meant to assess risk of interop or compat due to unresolved >> specification issues. The text is: >> >> *Open questions about a feature may be a source of future web compat or >> interop issues. Please list open issues (e.g. links to known github issues >> in the project for the feature specification) whose resolution may >> introduce web compat/interop risk (e.g., changing to naming or structure of >> the API in a non-backward-compatible way).* >> >> -- >> 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 blink-dev+unsubscr...@chromium.org. >> To view this discussion on the web visit >> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw8bORy9_hNLxmOkHhBBZ1%2BqX0jSWt5OCLaxhEQO2HM-8g%40mail.gmail.com >> >> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw8bORy9_hNLxmOkHhBBZ1%2BqX0jSWt5OCLaxhEQO2HM-8g%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > > > -- > Thomas Steiner, PhD—Developer Relations Engineer (https://blog.tomayac.com > , https://twitter.com/tomayac) > > Google Germany GmbH, ABC-Str. 19, 20354 Hamburg, Germany > Geschäftsführer: Paul Manicle, Liana Sebastian > Registergericht und -nummer: Hamburg, HRB 86891 > > ----- BEGIN PGP SIGNATURE ----- > Version: GnuPG v2.3.4 (GNU/Linux) > > > iFy0uwAntT0bE3xtRa5AfeCheCkthAtTh3reSabiGbl0ck0fjumBl3DCharaCTersAttH3b0ttom. > hTtPs://xKcd.cOm/1181/ > ----- END PGP SIGNATURE ----- > -- 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 blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/b3bf724c-54d9-493b-b135-8aa57dce506bn%40chromium.org.
