FireFox 1.5.0.6


Recommended Posts

mozilla.com still gives the 1.5.0.5 download link.

FIREFOX 1.5.0.6 IS NOT OFFICIALLY RELEASED YET!!! HOW MANY TIMES DOES IT NEED TO BE REPEATED?!?!

THEN DON'T DOWNLOAD IT!!!!!!eleventyone111

I?m thinking you forgot to take your Ritalin for today. If people want to download Firefox, then they will download it. Official or not, we'll install it. If this release is retracted and a newer one is released, then we'll download and install it as well. You make it sound like installing this will take down the Internet. Deep breaths man, deep breaths:):)

Even if its in the release folder doesnt mean that it's officially released. Officially released means the website has been updated. The copy in the release folder may very well be the final version, but as long as its not up on the website, there is still a chance that it might be changed before the official release, if they discover anything severe last minute.

It doesn't make sense for them to put a non-release version in the releases folder with all of the other official releases. Perhaps in your 16 years on this planet you haven't learned everything yet.

The changelog appears to be up on the site now (http://www.mozilla.com/firefox/releases/1.5.0.6.html). Only one change listed:

Firefox 1.5.0.6 is a stability update that is part of our ongoing program to provide a safe Internet experience for our customers. We recommend that all users upgrade to this latest version.

* Fixed an issue with playing Windows Media content

Release Date: August 2, 2006

Too bad it takes a few days for my auto updater to even detect a newer version even after the main page was updated.
That's strange. All the PCs that I own that run Firefox have already detected and been upgraded to 1.5.0.6.

It doesn't make sense for them to put a non-release version in the releases folder with all of the other official releases. Perhaps in your 16 years on this planet you haven't learned everything yet.

No, you are wrong. The release steps could go one of two ways.

First way

1. Builds are made that are thought to be final

2. Website updated to advertise new release, release notes posted, release made official

3. Builds start to get copied across the mirror network (can take hours)

In the meantime, people see that the website is updated but can't get an update because the mirrors aren't (all) populated. This would just wind people up and cause headaches.

The second way (which is the way it's done)

1. Builds are made that are thought to be final

2. All mirrors get copies of the files

3. When the powers that be are satisfied, the update goes live.

It's perfectly possible that between steps 2 and 3 a problem is found, or a respin done to fix some error. Jumping the gun between steps 2 and 3 could well mean you end up with a known buggy build, and standing on the rooftops shouting that a new version is out because it's on releases.mozilla.org will just encourage others to download the same buggy build.

Firefox is not out until the website is updated. Until then, the builds on the releases.mozilla.org servers could change. Assumption is the mother of all ****ups, and one day it will bite you on the ass.

No, you are wrong. The release steps could go one of two ways.

First way

1. Builds are made that are thought to be final

2. Website updated to advertise new release, release notes posted, release made official

3. Builds start to get copied across the mirror network (can take hours)

In the meantime, people see that the website is updated but can't get an update because the mirrors aren't (all) populated. This would just wind people up and cause headaches.

The second way (which is the way it's done)

1. Builds are made that are thought to be final

2. All mirrors get copies of the files

3. When the powers that be are satisfied, the update goes live.

It's perfectly possible that between steps 2 and 3 a problem is found, or a respin done to fix some error. Jumping the gun between steps 2 and 3 could well mean you end up with a known buggy build, and standing on the rooftops shouting that a new version is out because it's on releases.mozilla.org will just encourage others to download the same buggy build.

Firefox is not out until the website is updated. Until then, the builds on the releases.mozilla.org servers could change. Assumption is the mother of all ****ups, and one day it will bite you on the ass.

It makes perfect sense to test the build thoroughly before putting it in the releases folder for people to download. It would be bad practice to put it in there and then test it, that's what nightly's are for. Why would they even go though the trouble of distributing and untested package to the mirrors when it's possible that they'd have to do it again if a problem is found?

Your logic makes no sense but it doesn't matter, this isn't worth arguing with you about anymore.

It makes perfect sense to test the build thoroughly before putting it in the releases folder for people to download. It would be bad practice to put it in there and then test it, that's what nightly's are for. Why would they even go though the trouble of distributing and untested package to the mirrors when it's possible that they'd have to do it again if a problem is found?

Your logic makes no sense but it doesn't matter, this isn't worth arguing with you about anymore.

They're not untested (the files are *intended* for final release) but that's not to say something hasn't slipped through the net that'll get picked up before official release, and remedied with a respin.

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

    • No registered users viewing this page.
  • Posts

    • Would be good to see Google also being forced to do the same. No promotion of Chrome on Google search. Stop installing into the app data of a locked down machine, etc
    • FileZilla 3.70.6 by Razvan Serea FileZilla is powerful Open Source FTP/SFTP client with many features. It includes a site manager to store all your connection details and logins as well as an Explorer style interface that shows the local and remote folders and can be customized independently. The program offers support for firewalls and proxy connections as well as SSL and Kerberos GSS security. Additional features include keep alive, auto ascii/binary transfer, download queue, manual transfers, raw FTP commands and more. FileZilla key features: Cross-platform support – Available for Windows, macOS, and Linux. FTP, FTPS, and SFTP support – Handles standard and secure file transfer protocols. Tabbed user interface – Easily manage multiple connections at once. Site Manager – Save and organize server connection details. Drag & drop support – Quickly transfer files by dragging them. Filename filtering – Include or exclude specific files using filters. Directory comparison – Compare local and remote directories. Synchronized browsing – Navigate in sync between local and remote folders. Transfer queue – View, manage, and prioritize file transfers. Speed limits – Control upload/download speed to manage bandwidth usage. Keep-alive system – Prevents timeouts during long transfers. Remote file editing – Open and edit remote files using local editors. IPv6 support – Compatible with modern networking standards. FileZilla 3.70.6 changelog: New features SFTP: Added compatibility flag to Site Manager to ignore invalid bits in file attributes flags received from non-compliant servers Bugfixes and minor changes SFTP: Updated to fzssh 1.3.0 Updated to libfilezilla 0.56.1 Removed autodetection of FTP server type governing the remote path syntax. Exotic server types now need to be set explicitly on the advanced page in the Site Manager Download page: FileZilla 3.70.6 | ~10.0 MB (Free, paid upgrade available) Links: FileZilla Home page | Documentation | FileZilla Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Browser vendors pen open letter to Microsoft saying "enough is enough" by Usama Jawad We have seen Microsoft resort to questionable tactics in the past to get more customers to use Edge, such as "bribing" people to use Edge, testing new behavior so that Edge loads automatically on startup every time, and pressuring OEMs to exclusively bundle Edge in Windows PCs. However, the company often receives pushback not only from customers but also from the Browser Choice Alliance (BCA). Now, the collective has penned an open letter to the Redmond tech firm to highlight its dissatisfaction with its practices. For those unaware, BCA is a coalition that touts several browser vendors as its members, including Google Chrome, Midori, Opera, Vivaldi, BrowserWorks, and Wavebox. Its latest open letter to Microsoft CEO Satya Nadella emphasizes that "enough is enough" and that user choice on Windows should be respected. It claimed that the company is abusing its dominant position in the PC space to push customers to its first-party browser, even if they don't want to use it. To do this, it resorts to shady tactics, some of which we highlighted at the start of this piece. It says that Microsoft is making it very difficult for users to set their preferred browser across all touchpoints. This is problematic as PCs are becoming even more prevalent in the AI era, so user choice is being restricted across even more devices, further frustrating users (and competing browser vendors). As such, BCA has urged Microsoft to take the following actions to level the playing field: Allow browser suppliers to compete for preinstallation and default deals with Windows PC manufacturers End dark patterns targeted at users seeking to download and effectively use other browsers (including as system-level default) Bring back the ability for users to make switching default browsers simple and transparent with a “single click” change for all relevant file types and apps (including PDFs) Open all web links in the users’ selected system-level browser of choice Eliminate manipulative Microsoft-exclusive banners pushing Edge in Windows, including when users are searching for other browsers Stop using operating system updates to push users back to Edge Remove the restrictive configurations of existing S mode devices that block the usage of third-party browsers. It believes that all browsers should compete on merit, as this will drive innovation and healthy competition. Despite its strong wording and publication of the letter openly, it's unclear if Microsoft will pay any heed to the BCA and if this will result in any tangible downstream benefits. We'll likely find out in due time.
    • Boo! I was excited for this... Stargate SG-1 Star Michael Shanks Rallies Fans After Amazon Axes Revival, Says 'Now Is the Time to Say Something'
  • Recent Achievements

    • Conversation Starter
      mobandz earned a badge
      Conversation Starter
    • Apprentice
      fernan99 went up a rank
      Apprentice
    • One Month Later
      nothanks earned a badge
      One Month Later
    • One Month Later
      B2Proxy earned a badge
      One Month Later
    • One Year In
      MadMung0 earned a badge
      One Year In
  • Popular Contributors

    1. 1
      +primortal
      472
    2. 2
      PsYcHoKiLLa
      247
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      77
    5. 5
      Michael Scrip
      60
  • Tell a friend

    Love Neowin? Tell a friend!