It's been a bit of a zany day as we race towards a code freeze on Firefox 4 Beta 1, especially with the mozilla-central tree running out of disk space for a little while limiting our ability to check in code!
We have four blockers left, only three of which are code-related:
Gavin, Dao and Jim Mathies are working hard on those bugs, and we hope to get to resolution later tonight. I'll check back on this thread once it's done. With luck, we'll be starting builds tomorrow morning.
In the meantime, I'd like to ask everyone to hold off on risky code changes on mozilla-central.
> It's been a bit of a zany day as we race towards a code freeze on Firefox 4 Beta 1, especially with the mozilla-central tree running out of disk space for a little while limiting our ability to check in code!
> We have four blockers left, only three of which are code-related:
> Gavin, Dao and Jim Mathies are working hard on those bugs, and we hope to get to resolution later tonight. I'll check back on this thread once it's done. With luck, we'll be starting builds tomorrow morning.
> In the meantime, I'd like to ask everyone to hold off on risky code changes on mozilla-central.
> cheers, > mike
Well we seem to have some issues with today's nightly build as a result of the landing of Drawing in Titlebar. 1. No tool-tips show anywhere, bookmarks, tabs, 'Larry'... 2. On start-up a gray area where the UI should be, and its not painted until after the browser has fully loaded. 3. I've seen reports of images flickering when dragging the browser window, but I don't see that myself.
I point this out, in case other/further testing is needed before going forward with the 4.0 B1
> On Jun 24, 8:48 pm, Mike Beltzner <beltz...@mozilla.com> wrote:
> > followup-to: mozilla.dev.planning
> > Hello everyone,
> > It's been a bit of a zany day as we race towards a code freeze on Firefox 4 Beta 1, especially with the mozilla-central tree running out of disk space for a little while limiting our ability to check in code!
> > We have four blockers left, only three of which are code-related:
> > Gavin, Dao and Jim Mathies are working hard on those bugs, and we hope to get to resolution later tonight. I'll check back on this thread once it's done. With luck, we'll be starting builds tomorrow morning.
> > In the meantime, I'd like to ask everyone to hold off on risky code changes on mozilla-central.
> > cheers, > > mike
> Well we seem to have some issues with today's nightly build as a > result of the landing of Drawing in Titlebar. > 1. No tool-tips show anywhere, bookmarks, tabs, 'Larry'... > 2. On start-up a gray area where the UI should be, and its not painted > until after the browser has fully loaded. > 3. I've seen reports of images flickering when dragging the browser > window, but I don't see that myself.
> I point this out, in case other/further testing is needed before going > forward with the 4.0 B1
Iten 1, No tool-tips, is not totally true - its just that they appear in the taskbar - On win7 with 'previews' turned on, you see the Icon in the Taskbar flicker - showing something there... but when I tried viewing that it went away without being displayed. I tested this by clicking on 'Larry'...
> On Jun 25, 8:20 am, Littlemutt <jmjjeff...@gmail.com> wrote: >> On Jun 24, 8:48 pm, Mike Beltzner <beltz...@mozilla.com> wrote:
>>> followup-to: mozilla.dev.planning
>>> Hello everyone,
>>> It's been a bit of a zany day as we race towards a code freeze on Firefox 4 Beta 1, especially with the mozilla-central tree running out of disk space for a little while limiting our ability to check in code!
>>> We have four blockers left, only three of which are code-related:
>>> Gavin, Dao and Jim Mathies are working hard on those bugs, and we hope to get to resolution later tonight. I'll check back on this thread once it's done. With luck, we'll be starting builds tomorrow morning.
>>> In the meantime, I'd like to ask everyone to hold off on risky code changes on mozilla-central.
>>> cheers, >>> mike
>> Well we seem to have some issues with today's nightly build as a >> result of the landing of Drawing in Titlebar. >> 1. No tool-tips show anywhere, bookmarks, tabs, 'Larry'... >> 2. On start-up a gray area where the UI should be, and its not painted >> until after the browser has fully loaded. >> 3. I've seen reports of images flickering when dragging the browser >> window, but I don't see that myself.
>> I point this out, in case other/further testing is needed before going >> forward with the 4.0 B1
> Iten 1, No tool-tips, is not totally true - its just that they appear > in the taskbar - On win7 with 'previews' turned on, you see the Icon > in the Taskbar flicker - showing something there... but when I tried > viewing that it went away without being displayed. I tested this by > clicking on 'Larry'... > _______________________________________________ > dev-planning mailing list > dev-plann...@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-planning
I thought firefox-3.7 == firefox-4.0 not that it would upgrade but more of a name change - -- Sincerely Yours, John Vivirito
> On Jun 24, 8:48 pm, Mike Beltzner <beltz...@mozilla.com> wrote: >> followup-to: mozilla.dev.planning
>> Hello everyone,
>> It's been a bit of a zany day as we race towards a code freeze on Firefox 4 Beta 1, especially with the mozilla-central tree running out of disk space for a little while limiting our ability to check in code!
>> We have four blockers left, only three of which are code-related:
>> Gavin, Dao and Jim Mathies are working hard on those bugs, and we hope to get to resolution later tonight. I'll check back on this thread once it's done. With luck, we'll be starting builds tomorrow morning.
>> In the meantime, I'd like to ask everyone to hold off on risky code changes on mozilla-central.
>> cheers, >> mike
> Well we seem to have some issues with today's nightly build as a > result of the landing of Drawing in Titlebar. > 1. No tool-tips show anywhere, bookmarks, tabs, 'Larry'... > 2. On start-up a gray area where the UI should be, and its not painted > until after the browser has fully loaded. > 3. I've seen reports of images flickering when dragging the browser > window, but I don't see that myself.
> I point this out, in case other/further testing is needed before going > forward with the 4.0 B1
hey littlemutt;
Please file a bug, and mark it beta1? to make sure it gets looked at in time. Also, which OS you are seeing this on?
> Gavin, Dao and Jim Mathies are working hard on those bugs, and we hope to get to resolution later tonight. I'll check back on this thread once it's done. With luck, we'll be starting builds tomorrow morning.
Apparently we didn't do a good job at obtaining the luck!
As reported here, there have been a few pretty significant functional regressions which are being looked at. No builds for now. We may end up backing out the drawing-in-titlebar code and moving the Firefox button into the tabstrip so that we can get to a freeze.
Obviously things turned out to be less imminent than I'd hoped!
As shown in our blocker list ( https://bugzilla.mozilla.org/buglist.cgi?quicksearch=blocking1.9.3:beta1 ) we are basically done for Beta 1. This came thanks to some really great work in the finishing stretches driven by Jim Mathies, Dao Gottwald, Gavin Sharp and with the help of our QA, Engineering and nightly tester groups. We seriously could not have gotten here without your dedicated help, a lot of it over this past weekend.
I've asked the Sheriff to close the tree to allow some quiet time for the builds to go through the automatic testing, and will hopefully be able to issue a build order off of changeset http://hg.mozilla.org/mozilla-central/rev/6346fc0d0d61 a little later on today.
The tree will re-open soon, please be patient with this process.
Please also note that when it re-opens it will carry a new version number: Firefox 4.0b2pre / Gecko 2.0b2pre.
> Obviously things turned out to be less imminent than I'd hoped!
> As shown in our blocker list ( https://bugzilla.mozilla.org/buglist.cgi?quicksearch=blocking1.9.3:beta1 ) we are basically done for Beta 1. This came thanks to some really great work in the finishing stretches driven by Jim Mathies, Dao Gottwald, Gavin Sharp and with the help of our QA, Engineering and nightly tester groups. We seriously could not have gotten here without your dedicated help, a lot of it over this past weekend.
> I've asked the Sheriff to close the tree to allow some quiet time for the builds to go through the automatic testing, and will hopefully be able to issue a build order off of changeset http://hg.mozilla.org/mozilla-central/rev/6346fc0d0d61 a little later on today.
> The tree will re-open soon, please be patient with this process.
> Please also note that when it re-opens it will carry a new version number: Firefox 4.0b2pre / Gecko 2.0b2pre.
> Obviously things turned out to be less imminent than I'd hoped!
> As shown in our blocker list ( https://bugzilla.mozilla.org/buglist.cgi?quicksearch=blocking1.9.3:beta1 ) we are basically done for Beta 1. This came thanks to some really great work in the finishing stretches driven by Jim Mathies, Dao Gottwald, Gavin Sharp and with the help of our QA, Engineering and nightly tester groups. We seriously could not have gotten here without your dedicated help, a lot of it over this past weekend.
> I've asked the Sheriff to close the tree to allow some quiet time for the builds to go through the automatic testing, and will hopefully be able to issue a build order off of changeset http://hg.mozilla.org/mozilla-central/rev/6346fc0d0d61 a little later on today.
> The tree will re-open soon, please be patient with this process.
> Please also note that when it re-opens it will carry a new version number: Firefox 4.0b2pre / Gecko 2.0b2pre.
Several issues surrounding the bundled Feedback Add-On were discovered with Firefox 4 Beta 1 and have now been resolved. I've asked the release engineering team to move on to build 2, and instructed QA to pick up testing build 2 inline as there were no changes to code outside of the Feedback XPI.
(Note: please do NOT point people to the FTP site as the source of "Firefox 4 Beta 1" since these continue to be pre-release builds intended for QA and verification before shipping.)
