Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
mozilla.dev.planning
+ new post
About this group
Subscribe to this group
This is a Usenet group - learn more
Message from discussion Getting serious about finishing 3.1
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Graydon Hoare  
View profile  
 More options Feb 19 2009, 5:17 pm
Newsgroups: mozilla.dev.planning
From: Graydon Hoare <gray...@mozilla.com>
Date: Thu, 19 Feb 2009 14:17:43 -0800
Local: Thurs, Feb 19 2009 5:17 pm
Subject: Re: Getting serious about finishing 3.1
Print | View thread | Show original | Report this message | Find messages by this author
On 19/02/09 11:05 AM, L. David Baron wrote:

> 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


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2012 Google