Slashdot Mirror
Mozilla 1.4 RC3 Is Out
zzxc writes "Mozillazine reports that the third release candidate for Mozilla 1.4 has been released. It is available for download from mozilla.org. Testing is encouraged to fix any bugs before the final release. No new features have been added to this release, though many bugs have been fixed. For more information, see the release notes."
Another mozilla 1,4 rc story...
Don't you have any sco news?
I wish they would only put in the release notes the changes between RC2 and RC3 (and not between 1.3 and 1.4). Every time I read the release notes for the different RC's I get a strong dejavu. Must I really begin to diff them?
Mozilla 1.4 RC3 is expected to be the final release candidate. It incorporates the fix for one final GDI leak bug, and some minor stuff, but unless something completely unexpected will crop up, this very same release candidate will be rebranded as 1.4 final by the end of the week.
Firebird a subproject of Mozilla is a light weight version of Mozilla seems a lot better bet to me.
:)
Actually, the current Mozilla Roadmap clearly states this goal: Deliver a Mozilla 1.4 milestone that can replace the 1.0 branch as the stable development path, then move on to make riskier changes during 1.5 and 1.6. The major changes after 1.4 involve switching to Mozilla Firebird and Thunderbird, and working aggressively on the next two items.
So actually, that's where we're heading
.: Max Romantschuk
I've been using the the nightly builds since 0.5 was released. Mozilla Firebird is definitely *not* bug free (the releases are of course pretty stable), but I'm sure they could really use your help in testing it. :) The Firebird team has been really, really responsive about fixing bugs, and most bugs are usually fixed in the next nightly build.
My personal favorite feature is the ability to customize the toolbars. Admittedly, it's been a feature in Konqueror (my other favorite browser) since the beginning, but Firebird's toolbar customization is cooler as it supports drag-and-drop, while in Konq you have to use a Microsoft Office-style dialog box.
My journal has hot
When Moz 1.4 final is released, will Firebird then be based on 1.4, or will it remain based on the Moz 1.3 codebase? Also Moz needs better default fonts still. I had to install the vera fonts to make it look decent. In IE the fonts looks so much better. I know, thats becasue its using the fonts in windows and what not, and moz just can't include anti aliased fonts that won't work on systems x,y and z, but there needs to a system with prebuilt decent fonts. Moz is now so much better than IE, but default Moz on linux looks like a POS. Yes yes I installed truetype fonts now its fine but a lot of people don't know how to do all that. All this is becasue I had installed linux for a non computer person, who updated mozilla and then was stuck with the default fonts.
there is a great Gnome-Project wich adapts pretty fast to new Mozilla releases and ships with antialiased fonts (I didnÂt like them in the beginning but am an addict now ;-) called Dropline-Gnome. I keep installing this for my newbies along with Slackware wich I prefer as a Newbie-Distro for itÂs clear structure. From this day on I stopped worrying about fonts in Mozilla. Most Gnome Apps use these fonts so it provides a consistent look&feel, too.
But last time I tried Firebird I realised the problem was still there. The defaults are ok...but not a beauty. Well, if for non-slackware users I guess Ximian-Gnome ships with antialiased fonts as well...
Erm, I'd say ANY release candidade is expected to be the final. Otherwise, why's is it a candidate? In my book, RC means you've fixed all bugs you're aware of at that time, so unless some others crop up, that's going to be the final version.
Be wary of any facts that confirm your opinion.
If i check bugzilla there are currently 343 bugs open that are:
blocker or critical
and
assigned. (i did not select new 1441 bugs because they still contain dupes, or bugs that need te be cleaned).
That is a LOT! and they want 1.4 to be the next stable release for a longer time. I think it is still time forsome bugsquasing before releasing is.
LotÂs of these bugs are cross platform bugs (example:it wont build on true64,aix)
One bad bug i want to note is:209896
Bug: mozilla crashes if upgraded from 1.3.1 to RC2.
workround: uninstall first.
Yeah right: so every bug somebody calls (on some generic internet forum) the response will be: delete you mozilla directory first, then reinstall.
in mozilla, type something in the adress bar , press down key and you get "search google for" , press enter and boom results are there.
I don't want to switch to a different search field or even set up parameterized keywords to do this.. Google search with 2 keys (down + enter) is for me the killer feature as i do this well over a hundred times per day
But that's how it SHOULD work. A release candidate is a build which is expected to become the release. If you expect that it won't be the final build, it's a beta version, not a RC. You can trick users into installing RC builds a few times, but when they realize that the builds are just more "public betas", they will stop installing RCs and that will remove this important step from the feedback loop. Calling a build more mature than it is is also a bad move publicity-wise. People expect that the release is mostly the same as or only slightly better than the release candidate, so if you know about bugs which you deem inacceptable for a release build, don't make a release candidate before fixing them.