Care to pango?
One note about the recent firefox update in FC3, is that it is built with --enable-pango, as I mentioned in the update mail. Generally, this should not cause problems for anyone. If for some reason it does, though, you can temporarily disable pango by setting MOZ_DISABLE_PANGO. Please file a bug if you encounter any issues. I've been using it enabled for a long time, though, as have others, and I've not heard of any major issues so it should be all good.
Doomed
We are so dead. There is a huge storm coming this way. Turn your head to the left side, and you'll see a large skull head coming to eat us. Oh no!
Dichoto-merging
I'd like to remind people that it is important for things that get checked in on the 1.7 branch to also land on the aviary 1.0.1 branch, and vice versa. The obvious exceptions are for toolkit-only fixes, seamonkey-only fixes, etc. It makes things exponentially easier for the people who are trying to fight the good fight.
I have seen a few people get frustrated with this, especially when certain fixes have been asked to be backed out of a branch, and subsequently the other branch. I apologize profusely for this inconvenience, but it is a necessity. If there is an issue, or a patch to a core component which has landed only in one place, and needs to be landed on the other, please bring it up with me or someone else on drivers@mozilla.org. I am going to attempt to sort these out myself over the next few days, but could use some help.
"Support 2 browsers for the price of one" is very appealing to large companies. For that to work, we need to be feature-for-feature, bug-for-bug compatible between the two branches as much as possible. Firefox 1.0 and Mozilla 1.7 are both long-lived, stable branches. By helping ensure this happens, we can ease the adoption of Firefox, Mozilla, <insert Gecko-derived product here>, etc. Firefox 1.0 and Moz 1.7.5 are out the door, but we still need to continue the good fight.
