[webkit-dev] Enabling new features in WebKit + prefixing

[Ryosuke Niwa]

On Sun, May 12, 2013 at 10:34 PM, Mark Rowe <mrowe at apple.com> wrote:

>
> On 2013-05-04, at 15:32, Dean Jackson <dino at apple.com> wrote:
>
> > This is a brief summary of yesterday's discussion at the contributors'
> meeting. If there is no strong disagreement here then I'll add this to the
> wiki.
> >
> > New Features
> > ------------
> >
> > - The rule of sending an email to webkit-dev when you're about to start
> work on a new feature remains in place. The idea here is that the community
> can support or object to the feature even being in the tree.
> >
> > - Once the implementation of the feature is ready for use, send another
> email to webkit-dev announcing your intentions to enable the feature in
> nightly builds. How do you know when something is "ready for use”?
>
> By “nightly builds” do we mean “all ports in tip of tree”? If so, can we
> please say that instead? “Nightly builds” refer to a specific subset of
> builds produced from tip of tree and unless the intent is to enable the
> features for that subset alone, and no other builds, it’s confusing to
> phrase things in this way.
>

I agree with Mark. "Turning a feature by default" is a much better
description than "shipping in nightly builds" in that the person who sends
such an email usually doesn't have control over what will be "shipped" in
nightly builds anyway.

- R. Niwa
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-dev/attachments/20130512/73fa862e/attachment.html>