On Mon, Jul 13, 2009 at 10:47 AM, David Hyatt <[email protected]> wrote:
> I agree. We should formalize this as policy too in my opinion. Maybe > something time-based, e.g., if you have an implementation of a new Web > technology that is going to take > (1month?) to implement, then the feature > should be landed inside ENABLE ifdefs (that can then be removed when the > feature is sufficiently far along). > For Chromium this kind of time frame can be problematic, since there's pretty much no guarantee of when a WebKit trunk build could be shipped as (eventually) a stable Chromium/Google Chrome release. Even having an incomplete feature in the tree a few days can result in the incomplete feature getting shipped to web authors. There is a general problem here of "when is the WebKit trunk shippable by third-parties", which is an issue too large and hairy for me to get into, let alone propose concrete changes for. However, if we simply had a policy of "if a web author can detect and try to use the feature, but it doesn't work right yet, then put it under a flag", that would at least take care of this piece of the problem. PK
_______________________________________________ webkit-dev mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
