Closed Bug 689004 Opened 11 years ago Closed 11 years ago

Upgrading Firefox 3.6.x to latest release results in many updates

Categories

(Release Engineering :: General, defect, P3)

x86
macOS
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: limi, Unassigned)

References

Details

(couldn't find a component for the Updater, I know this is not directly installer related, so feel free to move it)

I just had the following experience helping someone update their old 3.6.x instance to the latest Firefox:

Start Firefox, check for updates, she's running 3.6.something (sorry that I don't have the exact version where we started, didn't think it would result in problems later).

Firefox 3.6.20 starts downloading.
We restart.
I check for updates.

Firefox 3.6.22 starts downloading.
We restart.
I check for updates.

Firefox 5.0.1 starts downloading.
We restart.
I check the About dialog.

Firefox 6.0.1 starts downloading.
We restart.
I check the About dialog.

We're at the end, and no updates are available.

Expected result: Getting 6.0.1 immediately, or (if it's necessary for some update reason), at least the latest 3.6.x, and then directly to 6.0.1. Going via 3.6.20, then 3.6.22, then 5.0.1, then 6.0.1 seems excessive — and also takes quite a bit of time for a user with an average internet connection.
Component: Installer → Release Engineering
Product: Firefox → mozilla.org
QA Contact: installer → release
Version: Trunk → other
The portion of this bug where you had 3.6.20 downloading and then had to download 3.6.22 is bug 353804. The remainder is either due to the versions required to update to before getting the next version, releng not creating an update yet to go from a specific version to the latest, or it is what has been decided by Firefox release drivers.
(In reply to Robert Strong [:rstrong] (do not email) from comment #1)
> The remainder is either due to the versions
> required to update to before getting the next version, releng not creating
> an update yet to go from a specific version to the latest

if there isn't an update to got from an older version directly to the latest, shouldn't firefox download all the patches in between in and apply them in order as a single step?
(In reply to Alex Limi (:limi) — Firefox UX Team from comment #0)

I agree it is teh suck to do so many hops, and it's not where we want to be either. We currently go 3.6.latest --> 5.0.1 --> latest because of the "billboard" that appears for the "major update" offer. At the moment, the only fully-translated set of billboards we have contains explicit references to version 5 (eg http://www.mozilla.org/en-US/firefox/5.0/details/). Bug 668108 will rectify that by creating more general billboard, but we're still waiting on some localizers. We can go 3.6.x -> latest when they're done.

(In reply to Byron Jones ‹:glob› from comment #2)
> if there isn't an update to got from an older version directly to the
> latest, shouldn't firefox download all the patches in between in and apply
> them in order as a single step?

I don't know about the app side, but the update server doesn't know how to do this. Even if we could, and have optimised to 3.6.x --> 3.6.latest --> latest, the 10+ MB to get to 3.6.latest is kinda wasted, because both hops are complete updates rather than patches/diffs. Now, you might say 'just download the last complete then' and I'd say 'that might work, if the 3.6.latest --> latest step is set as a background update, but usually we prompt and users have to opt-in'.
(In reply to Alex Limi (:limi) — Firefox UX Team from comment #0)
> Firefox 3.6.20 starts downloading.
> We restart.
> I check for updates.
> 
> Firefox 3.6.22 starts downloading.
> We restart.
> I check for updates.

Going from 3.6.20 -> 3.6.22 is intended, because it's a background update that gets users on the most secure version of the branch. We can't do 3.6.20 -> latest because that's (currently) an Advertised Update, meaning users have to accept it manually -- and if they reject it, they'll be on a version with known security holes. The best we can do here is 3.6.x -> 3.6.latest -> latest, which we _should_ be doing shortly after bug 668108 is fixed.
Depends on: 668108
Priority: -- → P3
We're now serving 3.6.23 -> 7.0.1 (the current for the next few hours). When we ship 3.6.24 & 8.0, we'll have a direct 3.6.24 -> 8.0 update path. We'll be doing similar going forward. As far as I can tell, this is FIXED!
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You rock, thanks!
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.