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."

3 of 335 comments (clear)

  1. Release Notes way too bloated by djpig · · Score: 5, Insightful

    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?

  2. Re:The big question is by ComaVN · · Score: 5, Insightful

    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.
  3. Re:The big question is by Anonymous Coward · · Score: 5, Insightful

    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.