On Thu, Feb 19, 2009 at 2:49 PM, Ojan Vafai <[email protected]> wrote:
> I don't think it makes sense to block releases to the stable channel > on new tests that we've never passed. I somewhat agree, but there is a caveat. When we add a feature, if it's completely broken and awful, we probably shouldn't consider it "shippable", even though nothing has regressed since the past release. For example, right now we have middle-mouse autoscroll, but it feels so lousy I would rather turn it off than push it to the stable channel. Similarly I would be uncomfortable with, say, shipping a version of Chrome that adds support for HTML5 databases, but uses 200 MB on your hard drive (or whatever) when you do anything. Fill in your own scenario here. To the degree that new upstream tests represent "stuff we're shipping should actually work as advertised", I would prefer not to defer it. PK --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
