> > But I think there really should be a limit:  I don't see why
> > Tracemonkey shipping for the first time in Firefox 3.1 in November
> > 2009 is any better than Tracemonkey shipping for the first time in
> > Firefox 3.2 in November 2009, and I think we have a lot of other
> > good work in 3.1 that we should be getting into the hands of our
> > users.

> Yeah, I have to concur here. Tracemonkey is really cool tech, and a
> remarkably quick initial development, but it's not the whole enchilada
> of the browser. There's no need to *remove* it -- it is certainly
> getting much more stable and fast -- but it feels reasonable to think
> about a 3.1 with TM turned off by default. Adventureous users can turn
> it on, and we can turn it right back on by default on the trunk / 3.2
> alpha work. Releases require compromise-logic, and there's good stuff in
> 3.1 being blocked by TM. Stuff that has strategic long-term implications
> for web content.

> It's not like we need significantly more public testing to *find* bugs
> in TM. There's a substantial list with a pretty constant input-rate from
> nightly testers, lots for the group to work on. A lot of those are
> serious bugs, regularly nightly topcrashers and such.

> -Graydon