The Christian comes forth on Good Friday
In response to my earlier post, and with the kind help of Christian Persch (chpe), I now have a working FC2 build of epiphany 1.2.10. It should hit the updates area sometime soonish I suppose, along with Mozilla 1.7.6 and devhelp, though with the holidays, it may take a little bit to have a release engineer notice it. Be on the lookout.
Packaging Help Wanted
Anyone out there who can help get epiphany working against the latest set of mozilla packages I just pushed for FC2? Help muchly appreciated here. The set of RPMs is currently living in our FC2 updates-testing directory.
Chasing Gecko
I am sort of exhausted after a three day affair of releasing updates for Firefox, Mozilla, and Thunderbird. RHEL versions 2, 3, and 4 got the first set of builds, then FC3, then rawhide. FC2 is close to ready, and as soon as epiphany compiles, will be pushed out the door. The thing that is sort of scary is how efficient I have become at pushing these. Maybe now that everything is done, I can get some much-needed sleep.
Politics is the skilled use of blunt objects
Looks like pink is annoyed at the current state of the 1.7 branch. All I can say is this time it really is soon. And note that its drivers, not the foundation (of which I am a member of the former, not the latter). Also, when we open for 1.7.7 checkins, please note that any patches to anything in core Gecko will need to land on both the 1.7.7 and aviary 1.0.3 branches, or none at all.
On a somewhat related tangent, it should be noted that as the stable branches live on, we should be striving to reduce the number of checkins to it. At this point, I think we should not be taking many "bug" fixes, and limiting them to the more critical fixes. There probably will be some low-risk bug-fix patches going in, at which point, I'd be inclined to push in some of the low-risk patches I have in my 1.7 RPMs. I went to dinner a few nights ago with a few people and we discussed the issue of long-lived stable branches. What does "stable" mean? To many open source developers, it means "no bugs." But to the enterprise customer, it means "not changing." This is kind of a hard concept to grasp at first. Why would someone balk at the chance of a simple, low risk bug fix? The answer is quite simple though when you get down to it. They have already figured out there is a bug, and have worked around it. By "fixing" the bug, many times their workaround will break. Not really cool for a "stable" branch. Another way to look at it is in terms of people. Whom would you call more stable, the person whose personality changes constantly, or the person whose personality stays the same?
Mozilla 1.7.6 Status
We're getting close to a 1.7.6 release. There's just one more bug we need to get fixed, but in the meantime, if people can go ahead and test some builds, that would be awesome. To further that process, I've gone ahead and created some RPMs for rawhide. Get them from my rawhide repository.
Rebuilding
We're rebuilding all packages in rawhide against the gcc4.0 tree, and that means Firefox, Mozilla, etc. all get to play. There were a few places we fall down go boom on, but not as many as I'd expected. Most of the issues were on 64bit architectures. There will be a firefox version in rawhide tomorrow against gcc4 (1.0.1-4). Have fun with it, and report problems to RH Bugzilla.
2,304,000 pixels
So, I've found a few 1920x1200 Firefox wallpapers out there, but would love to see more. Some Thunderbird ones would also be nice. Anyone?
I Choo-Choo-Choose You
Here's a friendly reminder to those who aren't familiar with the GTK2 file chooser, and have noted that in Mozilla's implementation you apparently “can't” open hidden (dot-files) or type in a location. You can do both, actually. You can right click on the file list to choose both options. Additionally, you can press Ctrl+L or / to activate typeahead find.
