Firefox 3.5 Final Builds are now "Nightly out"

By bogas04
in Web Browser Discussion & Support

 Share

Recommended Posts

Community Regular

code.kliu.org

Posted
Posted (edited)

No. Unless a showstopper forces a respin (which is extremely unlikely at this point), the June 24 build (RC3) is the Final build. As I've said before in another thread, Mozilla does true candidates, which is why none of the RCs contain "RC" in the version info.

The tree has long been closed, and all checkins since June 24 have been things that are not a part of the build. The nightlies are automatically spun every day, regardless of whether there has been any changes to the code, and they will continue to be automatically generated every day after 3.5 is released (at which point, they will be 3.5.1pre).

Edited by code.kliu.org
Grand Master

boogerjones

Posted
Posted
As I've said before in another thread, Mozilla does true candidates, which is why none of the RCs contain "RC" in the version info.
Which is interesting in the world of software development. I was ridiculed on another thread for pointing out that Mozilla's release candidates are truly candidates for release, unlike other software, like say Windows, where release candidates have absolutely zero chance of being final.
Grand Master

ViZioN

Posted
Posted
Which is interesting in the world of software development. I was ridiculed on another thread for pointing out that Mozilla's release candidates are truly candidates for release, unlike other software, like say Windows, where release candidates have absolutely zero chance of being final.

It's a bit like comparing apples and oranges though isn't it? Although I see your point.

Grand Master

+Ryster Subscriber²

Posted
  • Subscriber²
Posted
Which is interesting in the world of software development. I was ridiculed on another thread for pointing out that Mozilla's release candidates are truly candidates for release, unlike other software, like say Windows, where release candidates have absolutely zero chance of being final.

You're right. With Windows, they generally pre-announce how many release candidates there will be. That, by the very definition of the term 'release candidate', means that they are not release candidates at all. How can RC1 be called a Candidate for Release if you've already announced there will be an RC2 long before RC1 came out. It's stupid really.

Microsoft should continue with the Beta tag until they are at the quality bar where the product could be released. At that point you compile a build and called it RC1. Assuming no show stoppers are found by the public in RC1, you use that very same build and rename it to Final. If bugs are found, you fix them and release a second RC. It's a no-brainer really.

Mozilla seems to do it this way which is a welcome change from Microsoft's backwards way of doing it.

Community Regular

code.kliu.org

Posted
Posted
Thanks, but I'll wait for the final version. :)

Which, from the looks of it, will almost certainly be bit-for-bit identical to RC3. ;)

For Mozilla, the process can vary. As people would recall, the Firefox 1.0 RCs were really glorified betas and were not true candidates. The current project drivers very much like the idea of a true RC (in part because it makes it easier for QA to sign off on things: if you spin a new build after an RC, you need to test that build anyway to make sure something weird didn't happen during build or packaging, etc.).

As for Microsoft, they have intentionally "grade-inflated", and they have a very good reason to do so. Raymond Chen wrote an article explaining this (sorry, don't have the link handy) that basically boiled down to this: Microsoft had a problem where people didn't pay attention to the betas, and there was one incident, back when Microsoft's RCs were true candidates that they got an important piece of feedback only after the RC came out, at which point it was too late in the process to make those sorts of changes without incurring a lot of extra cost. So they had to grade-inflate, and what used to be late betas are now RCs, and what used to be RCs are now escrow builds. The idea is that more people are more willing to test and give feedback if it says "RC" than if it says "beta". Though I think that with the current overuse of the "beta" label (e.g., Google's notorious perpetual betas), the need for this grade inflation has decreased somewhat in recent years.

Grand Master

M_Lyons10

Posted
Posted
You're right. With Windows, they generally pre-announce how many release candidates there will be. That, by the very definition of the term 'release candidate', means that they are not release candidates at all. How can RC1 be called a Candidate for Release if you've already announced there will be an RC2 long before RC1 came out. It's stupid really.

Microsoft should continue with the Beta tag until they are at the quality bar where the product could be released. At that point you compile a build and called it RC1. Assuming no show stoppers are found by the public in RC1, you use that very same build and rename it to Final. If bugs are found, you fix them and release a second RC. It's a no-brainer really.

Mozilla seems to do it this way which is a welcome change from Microsoft's backwards way of doing it.

I agree. I never understood Microsoft's way of doing this. It really doesn't make any sense at all.

Perhaps. It's only a day away, anyway. I think I can hold out with version 3.0.11 until the version 3.5 is released. :p

Yeah, I really can't wait. I still think that the Tab Previews they chose would have been better served if they used Showcase Tab as a base instead of the add in they chose, but that's my only gripe, and is admittedly miner. Showcase though is an AMAZING add in though.

This topic is now closed to further replies.
 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.

  • Posts

    • Why you need to take back control of your synced passwords and how to go about doing that

      By +Warwagon · Posted

      I love syncback!
    • Politically funny images of the World

      By +primortal · Posted

    • Get $50 of aloSIM Mobile Data Traveler eSim credit for just $24.97

      By News Staff · Posted

      Get $50 of aloSIM Mobile Data Traveler eSim credit for just $24.97 by Steven Parker Today's highlighted deal comes via our Apps + Software section of the Neowin Deals store, where you can save 50% off aloSIM Mobile Data Traveler Lifetime eSim Credit: Pay $24.97 for $50. Stay connected affordably in 120+ countries/regions with your own lifetime eSIM! An eSIM is a digital SIM card. It's basically just mobile data. Once it's activated on your device, it can connect you to data networks in other countries – giving you an internet connection with NO roaming charges. With aloSIM, you can load prepaid eSIM data packages onto your phone, tablet, or computer. Your lifetime eSIM never expires, so it's yours forever and there are never any monthly charges. You'll get $50 in eSIM data credit, which is almost always enough to cover all your data roaming needs for a full year. But if you run out of data, you can always top up your lifetime eSIM and stay connected internationally. Pay $24.97 for a lifetime eSIM with $50 in travel data credit Use your eSIM to join data networks in 120+ countries Install your lifetime eSIM on a compatible device to roam on local data networks Your lifetime eSIM never expires, and can be topped up with more data anytime Many data packages cost as little as $4.50 and last 7 days. Depending on the package you choose, the length of time varies. Good to know Length of access: lifetime For NEW customers only Instant digital redemption Once you add your $50 credit to your aloSim account you have up to 12-months to use it — after that your credit will expire When you pay for a data plan you also get a free phone number (via Hushed) for the same duration of your plan that was purchased - IE 7 day eSim plan gives you a free 7-day phone number Purchased coupon must be redeemed and used within 12 months This deal is not stackable (one offer per aloSIM account) A $4.50 data package will last 7 days The data DOES expire, and you WILL NOT have any leftover data for your next trip unless it takes place within the validity period. While the eSIM never expires, the actual data package is only valid for the length of time stated at purchase (i.e. seven days after activation, 30 days after activation, etc.) So if you buy a seven-day package and only use a tiny bit, that package is still going to expire after seven days. Access options: mobile (check compatibility) Max number of device(s): 1 Updates included Here's the deal: This aloSIM Mobile Data Traveler eSim $50 Credit normally costs ... $50, but it can be yours for just $24.97 for a limited time, a saving of $25 (50% off). For specifications, and license info please click the link below. Get this aloSIM Mobile Data Traveler eSim for just $24.97 (was $50) Although priced in U.S. dollars, this deal is available for digital purchase worldwide. Support queries If you have queries or need support for any of the Neowin Deals, please use the contact form here. Neowin Deals are managed and sold by StackCommerce who represent Neowin on an affiliate basis. Why we post these deals We post these because we earn commission on each sale so as not to rely solely on advertising, which many of our readers block. It all helps toward paying staff reporters, servers and hosting costs. So for those that keep moaning and complaining, be thankful we're still online for you to even do that. Other ways to support Neowin Whitelist Neowin by not blocking our ads Create a free member account to see fewer ads Make a donation to support our day to day running costs Subscribe to Neowin - for $14 a year, or $28 a year for an ad-free experience Disclosure: Neowin benefits from revenue of each sale made through our branded deals site powered by StackCommerce.
    • The Microsoft Office feature that time forgot

      By Fraud OS 11 · Posted

      WordArt was cool. We now have color fonts as a substitute although Word only supports COLRv0 and COLRv1 (Fraud OS 11 only). The OpenType SVG color font format needs to be supported by Office. Adobe's apps support it
    • Why you need to take back control of your synced passwords and how to go about doing that

      By fintechfooty · Posted

      i backup my files, incl keepass to my proton drive using Syncback which i paid for (thanks Warwagon!). they have a free version but i can't remember what it does and doesn't do anymore. anyways, it's really, really simple and easy to use. i also periodically keep backups of my keepass onsite especially when i've changed or added a password that is important to me. if you don't wanna spend time on the syncthing setup, get syncback. haha i even got my dad to use it for his backups to usb and he doesn't even need my help!!! (thank god!)

  • Recent Achievements

    • First Post
      DrWankel earned a badge
      First Post
    • Reacting Well
      DrWankel earned a badge
      Reacting Well
    • Week One Done
      Supreme Spray LV earned a badge
      Week One Done
    • One Month Later
      Genuinetonerink- Dubai earned a badge
      One Month Later
    • Week One Done
      Genuinetonerink- Dubai earned a badge
      Week One Done

  • Popular Contributors

    1. 1
      +primortal
      497
    2. 2
      +Edouard
      158
    3. 3
      PsYcHoKiLLa
      90
    4. 4
      Steven P.
      74
    5. 5
      Michael Scrip
      72
    Show More

  • Tell a friend

    Love Neowin? Tell a friend!