More on Firefox 1.5, and “release candidates”

I wondered why I didn’t get the auto-update prompt, and so I went and got the 1.5 final version from the FTP site. I installed it, and… the build number is exactly the same as RC3. Which means, apparently, that 1.5RC3 and 1.5 final are the same!

This is what a release candidate should be - a candidate for the final version, which, if no new bugs are discovered, becomes the final version (otherwise, those bugs are fixed, and a second RC is released). But I’ve got so much used to the fact that “release candidate”, to most software authors, means just “what comes after beta” or “we can’t keep calling them betas forever”, that I didn’t even think that they would be using the term properly here! :)

Related posts:

  1. WordPress 2.0 RC
  2. Firefox 1.5 RC3
  3. Firefox 1.5 beta 2
  4. Firefox 1.5 Release Candidate 1!
  5. Firefox 3.0 beta 4

2 Responses to “More on Firefox 1.5, and “release candidates””


  1. 1 andr3

    I think even the checksum of both installs coincide. And yes, that’s the way it should be done. The last RC becoming the final release version. :)

  2. 2 bonus

    Maybe the choice may be difficult for PC users.. but for me on MAC, Firefox is definitely the best browser. IE for Mac is SO SLOW it makes no sense to use it.

Leave a Reply




Creative Commons Attribution-NonCommercial-NoDerivs 2.5 Portugal
Creative Commons Attribution-NonCommercial-NoDerivs 2.5 Portugal