[Webkit-unassigned] [Bug 222885] Formalize rules for what is an Experimental Feature

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=222885

--- Comment #20 from Maciej Stachowiak <mjs at apple.com> ---
(In reply to Sam Weinig from comment #18)
> The only reason the "other" option is "internal features" is that is the
> only other group we have that is automatically exposed. We can quite easily
> add more categories(In reply to Sam Weinig from comment #17)
> > (In reply to Maciej Stachowiak from comment #13)
> > > (In reply to Sam Weinig from comment #1)
> > > > I propose the following rules:
> > > > 
> > > > Experimental Features are:
> > > > 
> > > > - Features that have not shipped in an official release.
> > > > - Off by default (this means that if the experiment is disabling something,
> > > > it should be phrased as a negative, e.g. Disable SQL Databases)
> > > > - Stable enough that we would like people to try them out.
> > > 
> > > What would be the correct status for a feature that meets this first two of
> > > these criteria but not the third (but which does have a runtime feature
> > > flag)?
> > 
> > It could either be an internal feature or an unannotated feature.
> 
> Or a we could add a new category of toggle-able shipped features for it to
> go in.

By assumption, a feature like this would not be "shipped". To be clear, I was asking about a feature that has not shipped in an official release, is off by default, but is _not_ stable enough for it to be on by default. I'm not sure what the category of "unannotated feature" implies but maybe it's a fit.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20210323/e6ea5d0c/attachment-0001.htm>