On Sun, Dec 7, 2014 at 5:39 PM, <[email protected]> wrote: > Thanks Dmitry. I like the enhanced level of control the feature-shipping > process now exposes. One piece of feedback: in about:flags the labelling > for "#disable-javascript-harmony-shipping" is *Disable latest stable > JavaScript features.* > > For a developer familiar with blink-dev/v8-user lists, they could probably > determine that features this actually references. For those that are not, > it may appear confusing what we mean by "latest stable". Is there anything > we can do (link to docs, log disabled feature list to console) to better > indicate what features would be disabled using this user flag? >
Some better indication will be good. Unless you see something easy though, I do not think it is really worthwhile to invest into something elaborate here - this flag is really just a safety valve. Shipped feature is shipped - we do not have a list of "all Javascript features we implement" anywhere in the product. One reasonable place to disclose this information might be https://www.chromestatus.com/. I'll look into it. > > On Friday, December 5, 2014 3:53:30 PM UTC, Dmitry wrote: >> >> We are refining the procedure for shipping new Javascript features in V8, >> and, subsequently, in Chrome. >> >> 1. After the Javascript feature is shipped (following our process [1]), >> we will keep maintaining its enabled by default '--harmony-<feature>' flag, >> so that the feature can be turned off at runtime with >> '-noharmony-<feature>'. >> We will maintain this flag until we are sufficiently sure that the >> feature does not break even the remote long-tail corners of the Web - in >> practice that means at least one, and more likely two stable Chrome >> releases. >> >> 2. In V8, we introduce a '--harmony-shipping' flag, enabled by default. >> '--noharmony-shipping' will turn off all Javascript features for which we >> still maintain a flag [2]. >> >> 3. In Chromium, we expose an 'about:flags' flag >> 'disable-javascript-harmony-shipping' to the same effect [3]. Individual >> shipping features can be disabled by passing "--noharmony-<feature>" flags >> as part of Chromium's --js-flags as well. >> >> Currently in V8 we ship two features under this new regime: >> - ES6 numeric literals (--harmony-numeric-literals) >> - ES6 String functions (--harmony-strings). >> >> We introduce these measures to provide a safety valve for emergency >> situations such as http://crbug.com/409858. >> Our shipping and staging criteria for features, as defined in [1], are >> unchanged. >> >> Dmitry, >> on behalf of V8 team >> >> >> [1] https://developers.google.com/v8/launchprocess >> [2] https://chromium.googlesource.com/v8/v8.git/+/ >> 9e02e98771dcb00ed7332eaeeb78464a8b87afe5 and https:// >> chromium.googlesource.com/v8/v8.git/+/293f898a6f49f902c3cc5a4acaa7bf >> 6f2984e633 >> [3] https://crrev.com/a893e97a8453850e84be32c27c4f35b3be679054 >> > -- -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
