Recommended Posts

But it wasnt Here two days back

No... *sigh*.

The nightly builds are the builds that mozilla release Nightly in the development process, leading up to the full releases when the code has been signed off.

Any true releases will be under the releases directory.

Well, for people who follow Bugzilla, you'd know that RC3-build1 was basically dead-upon-arrival because of that final JIT crasher that was still unresolved when build1 was spun; shortly after build1 was spun, that bug (the final blocker) was fixed, and now we have build2. Unless another showstopper bug comes up (highly unlikely), RC3-build2 will be RC3, and RC3 will be Final...

So this nightly uploaded Build 2 is close enough to RC3 and thus very close to Final...?

Mozilla does true candidate builds. As in they'll spin RC3-build2. If they like it, then RC3-build2 is RC3 (they don't make a new build after they sign off on it--that specific candidate build is RC3. And if they find no showstoppers in RC3, then RC3 is Final. You'll notice that nowhere in RC3 does it say "RC3" because if RC3 looks okay after a period of time as a candidate, it will become Final. Once again, they don't go and spin another build--that specific RC3 build is final.

Not everyone does it this way (any software maker whose RCs say "RC" need to respin for Final to, at the very least, remove the "RC" from the version string), and every time there's a new major release of Firefox, a lot of people try to upgrade from RC and Final, not realizing that the are literally the same bits.

So IF no major showstopper comes out, RC3-build2 is literally, bit-for-bit, Final.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.