FireFox 1.5.0.6

[strotee]

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:):)

[Stokkolm]

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.

[Island Roots]

The more updates the safer I feel.

Changelog will appear here when live.

(Y) Ditto - with an update system as smooth as that of Firefox, I don't mind updating frequently. :)

[L3thal Veteran]

Too bad it takes a few days for my auto updater to even detect a newer version even after the main page was updated.

[Bhav]

I think that's the case with everyone's updater.

[dead.cell]

Too bad it takes a few days for my auto updater to even detect a newer version even after the main page was updated.

QFT.

[Island Roots]

Too bad it takes a few days for my auto updater to even detect a newer version even after the main page was updated.

It usually recognizes it for me on the same day - it updated my Firefox install about 30 minutes ago.

[Cyber Dog]

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

[Shof]

Just pop up

[Xerxes]

Cool thx for the heads up :) I could of sworn I read somewhere that 1.5.0.5 was going tobe the last update before the release of Firefox 2.0 :/ doesn't matter anyway :p

[UNCcrombie]

anyone know why whenever i install firefox on my hp laptop the screen jumps up and down? its only on that computer and doesnt do it on my pc

[L3thal Veteran]

It usually recognizes it for me on the same day - it updated my Firefox install about 30 minutes ago.

Well congratulations, my friend. It still hasn't popped up here and I don't expect it to for another day or two.

[golfantastic]

it popped up for me here!

[Quillz]

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.

[L3thal Veteran]

That's strange. All the PCs that I own that run Firefox have already detected and been upgraded to 1.5.0.6.

I suppose my Firefox is slower than yours? :blink:

[Island Roots]

Well congratulations, my friend. It still hasn't popped up here and I don't expect it to for another day or two.

With that attitude it won't! :laugh:

[RangerLG]

I just did a check for upgrade from the help menu. Popped up with the upgrade notice.

[thollian]

my work computer popped up, the moment I sat down and got on it...and said a new version of Firefox is ready to download...

[illicit]

Thanks for the update. :)

[acedriver]

anyone know why whenever i install firefox on my hp laptop the screen jumps up and down? its only on that computer and doesnt do it on my pc

mostly because of an empty bookmark toolbar folder..

[fels]

The reason, IIRC, why everyone's update is different is to not hammer their servers.

[kaffra]

thanks for the news, i was thinking it was my connection problem while steaming some videos

[+Cryton Subscriber²]

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.

[Stokkolm]

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.

[+Cryton Subscriber²]

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.