On Thursday 2011-03-03 13:29 -0800, Mike Shaver wrote: > On Thu, Mar 3, 2011 at 1:21 PM, L. David Baron <[email protected]> wrote: > > * meet all of the review criteria for landing in mozilla-central > > > > * entirely or primarily within the layout/ directory > > > > * safe enough that you'd be comfortable shipping them in a beta > > release (for, say, Firefox 5) after a week or less of nightly > > testing > > I think that anything non-trivial needs to also have a plan for > turning it off.
What sort of plan for turning things off would you expect for somewhat architectural performance improvements like these: https://bugzilla.mozilla.org/show_bug.cgi?id=636029 https://bugzilla.mozilla.org/show_bug.cgi?id=636039 These are things for which we have pretty solid test coverage, but there is a risk of some small (but easily fixable) regressions, and I don't see a realistic way to plan for turning them off other than planning to back them out. I'd much rather intermingle other things with these than the alternative, which is basically rewriting the patches at some later point, since they're going to be quite painful to merge with any new CSS property support. -David -- L. David Baron http://dbaron.org/ Mozilla Corporation http://www.mozilla.com/ _______________________________________________ dev-tech-layout mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-layout
