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 Firefox 3.1: Beta 3 proposal
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
 
Justin Wood (Callek)  
View profile  
 More options Nov 28 2008, 9:02 pm
Newsgroups: mozilla.dev.planning
From: "Justin Wood (Callek)" <Cal...@gmail.com>
Date: Fri, 28 Nov 2008 21:02:27 -0500
Local: Fri, Nov 28 2008 9:02 pm
Subject: Re: Firefox 3.1: Beta 3 proposal
Print | View thread | Show original | Report this message | Find messages by this author

Christopher Blizzard wrote:
> Mike, thanks for the mail.

> We still want to make the promise to add-ons developers that beta2
> will be "stable enough" to start mass converting add-ons, and your
> email does mention this.

> It follows in my mind that by making this statement we're committing
> to keep major functionality after beta2.  For example, it would be bad
> if someone wants to take advantage of DOM worker threads in their
> add-on, and we pull it before beta3.

My only concern here is suddenly it seems a majorly wanted feature for
SM2 (which will base off 1.9.1) was just backed out due to a possible
test failure, (harder for patches author to figure out since test was
mac-only, we'll try to figure it out though).. anyway, its a patch that
had been waiting for gavins review since before b1, (as in quite a long
while) he just reviewed it, but it does have potentially addon breaking
changes...

See Bug 407725 for the bug I talk about.
And Bug 467045 for an actual addon that broke due to that landing.

Will SM be able to have time to investigate and still get this in? (if
nothing else than because we've tried so hard to get the bug fixed) ;-)

[even better if because: it appears (to me, but again hard to test
locally) that the test failure failure due to a perf increase in a
mini-race-condition]

--
~Justin Wood (Callek)


 
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