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."
you forget those of us who use the mail client. firebird doesnt have mail/chatzilla/etc.
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?
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.
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.
If I am saying 1.3.1 i do not say nightly build.
/. . They are trying to help you, but if a bug exists "uninstall first" this is what they will always reply, even if the problem the reporter is heaving has nothing to do with XDOM dllÂs
1.3.1 happens to be the previous stable release. As is said in the comments of this bug: Why cannot clean the installer the old directory.
Answer from developer:
How to prevent data-loss if something (user-mail) is in that directory.
i think if you leave this to the user he sure is going to delete the wrong data.
AND YES I AM WORKED UP ABOUT THIS. Try posting something about a bug here on
Try telling here (i am not talking about bugzilla in the "every bug line) about some bug. They will point to the release notes:
"Install into a new empty directory. Installing on top of previously installed builds may cause problems."
That is an easy way to work around bugs. Just say "donÂt do that" in the readme.
And yes, i think it is strange there are critical bugs in a release candidate. These should be demoted to not important or the thing should still be called a beta.... AND/OR the bug should be explained in the readme. Still time for a 1.4.1. RC4 ?
(by the way, if you think that was a troll then never reply to it.)
What do you mean you don't want to switch search fields??? You obviously had to consciously say "I want to do a search" at some point and click on the address bar before you typed the search terms, the location bar does not constantly have the keyboard focus. What difference does it make if you click the address bar or the search box?
Has anybody noticed that Firebird gets progressively slower as your cache increases? I find that when I do a fresh install, the browser is snappy, and generally faster than IE. Over time, however, I am forced to wait up to 5 seconds to load a page from a fast web server only a few hops from me.
Clearing the cache seems to fix the problem somewhat. I also reduced the disk cache size to 5MB. Has anyone else had a problem like this?
"Smoking helps you lose weight - one lung at a time" -- A. E. Neumann