Closed Bug 367234 Opened 17 years ago Closed 17 years ago

Enable update for Firefox 1.5.0.x to 2.0.0.y

Categories

(Toolkit :: Application Update, defect)

1.8.0 Branch
defect
Not set
normal

Tracking

()

VERIFIED FIXED

People

(Reporter: bugzilla, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.0.9) Gecko/20061206 Firefox/1.5.0.9
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.0.9) Gecko/20061206 Firefox/1.5.0.9

On several occasions it has been stated that FF 1.5.x would automatically update to 2.y using the automatic Software Update feature [1] over the "next few weeks". Yet Firefox hasn't prompted such a question to this day.


1) http://mozillazine.org/talkback.html?article=20112

Reproducible: Always

Steps to Reproduce:
1. Install FF 1.5.0.9
2. Run Firefox
3. Go to Help > Update Firefox (Hilfe > Firefox aktualisieren)
Actual Results:  
Message displayed stating no updates are available.

Expected Results:  
Message asking whether to update to version 2.y or not.

Maybe I'm just impatient, but considering the statement was made on October 24th, 2006, I'd consider this time span to be over now. Yet my FF never asked me.

Thus, I'm not sure the update mechanism is actually working. Someone please check. :)
That update path hasn't been enabled yet, so I'm morphing the bug to do that. 
Severity: major → normal
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows XP → All
Hardware: PC → All
Summary: Auto update 1.5.x to 2.y not happening. Broken? → Enable update for Firefox 1.5.0.x to 2.0.0.y
Version: unspecified → 1.5.0.x Branch
I forgot to say that I'm only a volunteer, and the update depends on decisions made by people at Mozilla. There has been some talk of scheduling it between the (approximately) monthly security releases, so as to go easy on the mirrors, and to enable sometime "this month or early february". But that's all tentative and subject to change.
I also haven't found any other bug which covers the auto-update from 1.5.0.x to 2.0.0.x. Strange because this missing point is still in the queue since last year.

Adding some people who can hopefully tell us more.
Severity: normal → major
OS: All → Windows XP
Hardware: All → PC
Version: 1.5.0.x Branch → unspecified
The MozillaZine article had it wrong.  We have not committed to any specific dates, and 1.5.0.8 was the first release that even had the required bits, and that shipped a couple weeks after Firefox 2.

The only official timing I'm aware of is "soon."  Its going to mean a lot of bandwidth and coordination, plus a lot of testing to be sure it all works as advertised.  Its not like we've forgotten.
Severity: major → normal
OS: Windows XP → All
Hardware: PC → All
Version: unspecified → 1.5.0.x Branch
In the case of IE6 -> IE7, Microsoft enabled updates "progressively". That is, they only enabled the update for a small percentage of people every day. It may be a interesting feature for the mozilla update infrastructure, for future transitions (2.0 -> 3.0). This makes transitions smoother, as servers don't get a big hit, and  if there's a important failure detected in the process, you can go back and disable the update until the problem is fixed.

BTW, i've lot of friends that are still using 1.5 but that have got IE7 in their hands. I know people is caring of this, but not updating 1.5 users to 2.0 may get back some users to IE (7)!
It's been widely publicised that the 1.5.0.x series will only be supported until April 24th, 2007. So if there will be an auto-update to the 2.0 series, I suppose it will have to be pushed out before then?
Major updates have been served to Firefox 1.5.0.x users for two days now. As I heard from Carsten no critical problems arised till now. I think we can finally close this bug.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
> Major updates have been served to Firefox 1.5.0.x users for two days now

woo-hoo!  verified.
Status: RESOLVED → VERIFIED
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.