The Official 20080610 [Branch] RC3 builds are out

[chob]

This branch thread is a one-off special for RC3 builds. One Mac-only landing since RC2, so Win and Linux builds are unchanged. (Although the Win32 installer has been resigned.)

Releases/Firefox 3.0rc3 release steps.

The Official Win32 20080610 [1.9.0 Branch] RC3 builds are out.

Hourly 1.9.0 Branch builds:
fx-linux-tbox-trunk (Lin) || XSERVE08 (Mac) || FX-WIN32-TBOX-trunk (Win) || Trunk Tinderbox || Trunk Bonsai
Hourly Builds Archive: Linux, Mac and Windows

Last update: 2008-06-11 -- 09:05 PDT = 16:05 UTC (all check-ins since 20080605)
The tree is Locked

Fixed:

1. #436575 [Core:Plug-ins]-Moz apps experience unkillable hangs after installing Mac OS X 10.5.3 (loading VerifiedDownloadPlugin.plugin) [Mac] (Checked in 2008-06-09 15:18)

Partial Landings/WIPs/Incoming:

None

Regressions/Annoying/Common bugs:

1. #422308[Toolkit:Breakpad Integration]-Breakpad does not catch crash when flash plugin is active [Win](Macromedia flash problem, fixed with flash 10 beta)

To copy your useragent+buildtime to clipboard, use the Nightly Tester Tools extension.
Get more out of the Javascript Console, see this page for Console²
If you're a daily tester then backup the valuable data in your profile !

Trunk fixes since branching for 1.5 (20050812) = ~ 14,993

Roadmap: Firefox 3.0 [200806]
Gran Paradiso Milestones: 3.0rc2(20080604 ~14,992), 3.0rc1(20080517 ~14,972), 3.0b5(20080402 ~14,183), 3.0b4(20080310 ~13,646), 3.0b3(20080212 ~12,986), 3.0b2(20071221 ~12,169), 3.0b1(20071120 ~11,630), 3.0a8(20070920 ~10,640), 3.0a7(20070803 ~9,820), 3.0a6(20070703 ~9,350), 3.0a5(20070607 ~8,940), 3.0a4(20070427 ~8,350), 3.0a3(20070323 ~7,930), 3.0a2(20070208 ~7,450), 3.0a1(20061208 ~6,750)

If you want bugs to be fixed, find the regressionwindow.
If you want the regressionwindow, download hourly builds and test them.
It really makes a difference if you do.
IRC channels: #firefox || #bugs

[dreimanis]

15 000 bugs fixed. now that is a lot. what is the reference point for this count?

thanks

[WildcatRay]

So, Steve,

Are you going to be doing a daily Branch thread like you did for Firefox 2's Bon Echo at its beginning?

[chob]

Not sure WildcatRay. When the tree's re-opened for the 3.0.1pre builds I expect there will be quite a lot of landings, but I'm not sure if they're just going to be regression/stability/security fixes, or maybe some polish or other more interesting fixes. I might maintain a daily build thread for the first point release and see how it goes from there.

But then I still have to get my head around how the 3.1 branch and the 4.0/moz2 trunk are related, and if 3.1 is using CVS or hg, and what kind of landings 3.1 will get and how often. It seems to me for 6 months after 3.0 is released we're going to have the 2.0 branch, the 3.0 branch, a 3.1pre branch and the 4.0/moz2 trunk all running in parallel, and that's a lot of things to track and test.

[WildcatRay]

I thought others have said that 3.1pre (and I assume 4.0/moz2) is Mercurial already, but I may be wrong. I would then also presume that 2 & 3.0.1 will be the last of CVS.

[polidobj]

mozilla-central is currently for 3.1. The 1.9.1 branch should only coincide with the 1.8.1 branch for a short time which will be between branching for 1.9.1 and when the six month after FF3 time comes. Then the 1.8.1 branch will cease to be used. They may wait to branch 1.9.1 as long as they can since the trunk work should not be held up by branching like in the past with the trunk work being done elsewhere already. And during that overlap time they may only do Firefox releases for highly critical security bugs on the 1.8.1 branch. In other words they probably won't retain the practice of having a 2.0.0.x release about every 6 weeks.

As for the true trunk work AFAIK that's off in separate development branches to be merged to mozilla-central. There's at least one for the Tamarin work. I'm not sure if other work like with the automated tools is happening on separate branches.

[WildcatRay]

Brian,

What you've said seems to coincide with the value of Mercurial over CVS. From what I recall, changes can be worked on separately/"off-line" and much more easily be merged back into the main trunk than trying to similarly with CVS. Of course, I could be wrong, too.

[chob]

OK, that all makes sense, thanks all!

[WildcatRay]

Your welcome.

[Kirk M]

I've seen a lot of complaints form Mac users that the Flash plugin (latest 9.0.X) does not function at all in RC3. I even have friends of mine who have Macs emailing me as to why all their Flashy content is gone. Has anyone else heard about this?

I'm not a Mac user so I can't test this but by what I've seen so far, it's a real problem. Has anyone posted on the forum about this that I'm not seeing or has someone filed a bug report yet?

[sansibar]

I've seen a lot of complaints form Mac users that the Flash plugin (latest 9.0.X) does not function at all in RC3. I even have friends of mine who have Macs emailing me as to why all their Flashy content is gone. Has anyone else heard about this?

I'm not a Mac user so I can't test this but by what I've seen so far, it's a real problem. Has anyone posted on the forum about this that I'm not seeing or has someone filed a bug report yet?

Works for me with Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; de; rv:1.9) Gecko/2008061004 Firefox/3.0 ID:2008061004), but I have an other error: http://forums.mozillazine.org/viewtopic.php?t=665327

[Kirk M]

Hey Sansibar,

As usual, none of these users who are complaining are bothering to state which version of OS X they're running and I'm still waiting to hear back from a couple folks as to which version of OS X they're seeing the problem on. I've already asked one person to post on this thread and include some basic data about their machine and OS X version.

Thanks for the reply and I've already seen a comment on another forum that it works okay in 10.5. Maybe we can narrow it down to which version has this problem.

[alex_mayorga]

I left Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9pre) Gecko/2008061105 Minefield/3.0pre ID:2008061105 with Flash 10,0,1,218 installed running overnight yesterday and this morning it has crashed without report and the computer reported the "low on virtual memory... increasing".
Is there anything I can do to try to catch a crash report if it happens again?

[teoli2003]

Crash report about flash are pretty useless as they just say "something in flash has crashed" (and in your case probably a new or malloc failed). That's the probelm of Flash, they don't have public symbols making debugging flash problem impossible for non-adobe people.

[Rigido]

I've seen a lot of complaints form Mac users that the Flash plugin...

Hi Kirk,
I will post my data as I go back home, right now I can just say that I'm using the latest nigthly build on OS X 10.5.3.