I had a brainwave (well, more like a duh moment) over the weekend about how to sneakernet the Firefox 6 repo updates to the G5 build system, which is still marooned from the Internet. (A parenthetical note about that: I've sent Time Warner the beginning pieces of a lawsuit and basically told them I'm walking away from the contract unless by some miracle the line's in this week. I'm quite certain it won't be. I'm getting bids for a T1, which I probably should have done in the first place; with luck, the downtime won't be more than a week or two more, and then Floodgap will be back in business with a super duper faster line.) So the iBook made several trips to the local Starbucks and back to the house, and several hateful cups of Zen tea later, TenFourFox 6.0 RC/final is built and this post is being typed in it.
I'm a little nervous about this release; there's been pretty much no time for serious conformance testing on all the architecture builds, although the iBook G4 checks out and so does the G5 (what I can test locally). So please thrash it. There's no new features in it, just fixes. The changesets for beta 1 still apply, so there is no new changeset package. If there is a serious showstopper, I did do a cursory security review of Firefox 5, so we can build a 5.0.2 for security parity purposes if needed.
For users new to TenFourFox 6, remember: plugins are disabled (see previous posts).
Looking ahead, Tobias (bless him) has already done just about all the porting work on Fx7 in advance and he says it seems to run really well on his G4. I have his changesets on one of the marooned servers, so as soon as I can snatch the Fx7 repo once it goes beta, we will work on that. I am quite concerned about Fx8, though. Mozilla has landed several changes to the build system that expect builds to occur on 10.6 (even though the build is ostensibly linked against the 10.5 SDK) and obliterate PPC references. This is unwindable (though it will probably hit the vanilla PPC builders such as MonkeyBoy and El Furbe), but may have other side effects, and a simultaneous change to require and use CoreUI for drawing UI elements is also of serious alarm to me as it means our Tiger widget code may no longer work even if we restore the old code. They seem to be having various issues with it, however, as you might expect from an Apple private interface, and I'm hoping they give up and punt it to Fx9.
Watch for a re-release tonight or tomorrow Pacific.