headers
Mike Beltzner | 3 Oct 18:36
Favicon

Firefox 3.1 Beta 1 / mozilla-central tree status

(reply/followup to dev-planning <at> lists.mozilla.org /  
mozilla.dev.planning)

Hi everyone,

We're still working through the regressions identified after code  
freeze on Tuesday; the work proceeds as quickly as possible, but is  
limited due to the time required to get the performance data. While  
this happens, the mozilla-central tree remains frozen.

So far we've managed to get the following two bugs removed from the  
critical path:

https://bugzilla.mozilla.org/show_bug.cgi?id=364315 - fixed
https://bugzilla.mozilla.org/show_bug.cgi?id=458047 - declared non- 
regression

which leaves the following:

https://bugzilla.mozilla.org/show_bug.cgi?id=458048 - Drag & Drop of  
tabs crashing browser with new API
https://bugzilla.mozilla.org/show_bug.cgi?id=458065 - Windows Txul/ 
Tdhtml regression, afternoon of 2008-09-29

left to work through. There may be one other, as well - please reply  
if you see that I'm missing something here.

In addition, we'd like to see the following land once those  
regressions are worked out:
(Continue reading)

Permalink | Reply |
headers
Mike Beltzner | 3 Oct 18:42
Favicon

Re: Firefox 3.1 Beta 1 / mozilla-central tree status

Adding a bug to the list of things to land post-perf work: the shipped- 
locales patch in https://bugzilla.mozilla.org/show_bug.cgi?id=458056

On 3-Oct-08, at 12:39 PM, Mike Beltzner wrote:

> (reply/followup to dev-planning <at> lists.mozilla.org /
> mozilla.dev.planning)
>
> Hi everyone,
>
> We're still working through the regressions identified after code
> freeze on Tuesday; the work proceeds as quickly as possible, but is
> limited due to the time required to get the performance data. While
> this happens, the mozilla-central tree remains frozen.
>
> So far we've managed to get the following two bugs removed from the
> critical path:
>
> https://bugzilla.mozilla.org/show_bug.cgi?id=364315 - fixed
> https://bugzilla.mozilla.org/show_bug.cgi?id=458047 - declared non-
> regression
>
> which leaves the following:
>
> https://bugzilla.mozilla.org/show_bug.cgi?id=458048 - Drag & Drop of
> tabs crashing browser with new API
> https://bugzilla.mozilla.org/show_bug.cgi?id=458065 - Windows Txul/
> Tdhtml regression, afternoon of 2008-09-29
>
> left to work through. There may be one other, as well - please reply
(Continue reading)

Permalink | Reply |
headers
Mike Beltzner | 3 Oct 18:45
Favicon

Re: Firefox 3.1 Beta 1 / mozilla-central tree status

Sorry for the churn/spam here ...

I added a section on the release tracking wiki page where we can keep  
tabs on the work remaining before the handoff to build. Instead of  
replying to the thread, please put your updates there, as it's likely  
easier to keep track of than an email thread:

https://wiki.mozilla.org/Releases/Firefox_3.1b1

cheers,
mike

On 3-Oct-08, at 12:42 PM, Mike Beltzner wrote:

> Adding a bug to the list of things to land post-perf work: the  
> shipped-
> locales patch in https://bugzilla.mozilla.org/show_bug.cgi?id=458056
>
> On 3-Oct-08, at 12:39 PM, Mike Beltzner wrote:
>
>> (reply/followup to dev-planning <at> lists.mozilla.org /
>> mozilla.dev.planning)
>>
>> Hi everyone,
>>
>> We're still working through the regressions identified after code
>> freeze on Tuesday; the work proceeds as quickly as possible, but is
>> limited due to the time required to get the performance data. While
>> this happens, the mozilla-central tree remains frozen.
>>
(Continue reading)

Permalink | Reply |
headers
Mike Beltzner | 6 Oct 17:36
Favicon

Re: Firefox 3.1 Beta 1 / mozilla-central tree status

Hello everyone,

The regressions we were investigating are now all fixed or have been  
deferred to post-beta (bug 458065) so we're on to follow-up landings  
before handing over the tree to release-engineering for tagging and  
building. Please see here for more details:

https://wiki.mozilla.org/Releases/ 
Firefox_3.1b1#Development_Work_Remaining

Rob, bz, and Ryan, please co-ordinate your landings with the Sheriff  
ASAP.

cheers,
mike

On 3-Oct-08, at 12:45 PM, Mike Beltzner wrote:

> Sorry for the churn/spam here ...
>
> I added a section on the release tracking wiki page where we can keep
> tabs on the work remaining before the handoff to build. Instead of
> replying to the thread, please put your updates there, as it's likely
> easier to keep track of than an email thread:
>
> https://wiki.mozilla.org/Releases/Firefox_3.1b1
>
> cheers,
> mike
>
(Continue reading)

Permalink | Reply |
headers
Mike Beltzner | 7 Oct 06:43
Favicon

Re: Firefox 3.1 Beta 1 / mozilla-central tree status

Hi again,

We've finished the additional landings, and will be holding the tree frozen over night to ensure that there
are no further regressions. If all goes as planned, we'll hand over to build tomorrow morning early EDT.

cheers,
mike
----- "Mike Beltzner" <beltzner <at> mozilla.com> wrote:

> Hello everyone,
> 
> The regressions we were investigating are now all fixed or have been 
> 
> deferred to post-beta (bug 458065) so we're on to follow-up landings 
> 
> before handing over the tree to release-engineering for tagging and  
> building. Please see here for more details:
> 
> https://wiki.mozilla.org/Releases/ 
> Firefox_3.1b1#Development_Work_Remaining
> 
> Rob, bz, and Ryan, please co-ordinate your landings with the Sheriff 
> 
> ASAP.
> 
> cheers,
> mike
> 
> On 3-Oct-08, at 12:45 PM, Mike Beltzner wrote:
>
(Continue reading)

Permalink | Reply |
headers
dvdventura | 3 Oct 21:03
Favicon

Re: Firefox 3.1 Beta 1 / mozilla-central tree status

sorry,i don´t speak english.

--------------------------------------------------
From: "Mike Beltzner" <beltzner <at> mozilla.com>
Sent: Friday, October 03, 2008 6:39 PM
To: "dev. planning" <dev-planning <at> lists.mozilla.org>
Cc: <dev-platform <at> lists.mozilla.org>; "dev-apps-firefox" 
<dev-apps-firefox <at> lists.mozilla.org>
Subject: Firefox 3.1 Beta 1 / mozilla-central tree status

> (reply/followup to dev-planning <at> lists.mozilla.org /
> mozilla.dev.planning)
>
> Hi everyone,
>
> We're still working through the regressions identified after code
> freeze on Tuesday; the work proceeds as quickly as possible, but is
> limited due to the time required to get the performance data. While
> this happens, the mozilla-central tree remains frozen.
>
> So far we've managed to get the following two bugs removed from the
> critical path:
>
> https://bugzilla.mozilla.org/show_bug.cgi?id=364315 - fixed
> https://bugzilla.mozilla.org/show_bug.cgi?id=458047 - declared non-
> regression
>
> which leaves the following:
>
> https://bugzilla.mozilla.org/show_bug.cgi?id=458048 - Drag & Drop of
(Continue reading)

Permalink | Reply |

Gmane