Closed Bug 1105566 Opened 10 years ago Closed 10 years ago

Stop offering Firefox/64 updates to Vista x64 users

Categories

(Release Engineering :: General, defect)

x86_64
Windows Vista
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: emk, Unassigned)

References

Details

Otherwise they will receive unworkable builds.
We need to offer updates for 32-bit Firefox, of course.
Summary: Stop offering updates to Vista x64 users → Stop offering Firefox/64 updates to Vista x64 users
Compat changes like this should NOT be made without having plans to deal with updates in place. These sorts of decisions are usually taken to the newsgroups first. It looks like XP needs to be blocked too, based on my read of bug 1094013, so I've gone ahead and done that too.

According to http://msdn.microsoft.com/en-us/library/windows/desktop/ms724832%28v=vs.85%29.aspx, Vista is 6.0 (as is Server 2008, so users on this OS will get no updates either). To block these users from getting updates, I created a Balrog rule as follows:
priority: 100
mapping: No-Update
backgroundRate: 100
product: Firefox
channel: nightly*
buildTarget: WINNT_x86_64-msvc
osVersion: Windows_NT 6.0,Windows_NT 5.2

This results in queries like https://aus4.mozilla.org/update/3/Firefox/14.0a1/20120222174716/WINNT_x86_64-msvc/en-US/nightly/Windows_NT%206.0.0/default/default/update.xml or https://aus4.mozilla.org/update/3/Firefox/14.0a1/20120222174716/WINNT_x86_64-msvc/en-US/nightly/Windows_NT%205.2/default/default/update.xml not getting updates.

We'll need to remember to create similar rules for Aurora, Beta, and Release channels if/when we start doing 64-bit Windows builds there.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
(In reply to Ben Hearsum [:bhearsum] from comment #2)
> Compat changes like this should NOT be made without having plans to deal
> with updates in place. These sorts of decisions are usually taken to the
> newsgroups first.

Sorry, I (mis)thought decisions were already taken when bug 604967 was closed.

> We'll need to remember to create similar rules for Aurora, Beta, and Release
> channels if/when we start doing 64-bit Windows builds there.

We have never shipped Win64 Aurora, Beta and Release. Firefox/64 was nightly only. So no XP/Vista x64 users will receive the updates.
(In reply to Masatoshi Kimura [:emk] from comment #3)
> > We'll need to remember to create similar rules for Aurora, Beta, and Release
> > channels if/when we start doing 64-bit Windows builds there.
> 
> We have never shipped Win64 Aurora, Beta and Release. Firefox/64 was nightly
> only. So no XP/Vista x64 users will receive the updates.

Sounds like we can relax the channel restriction in the rule and not need to do anything in future.
I think this change was a mistake. If users are using nightly64 on an unsupported OS version, it would be better if they got updated and then Firefox refused to launch, than if they were stuck on a random nightly forever. Then they can migrate back to nightly32 and will at least continue receiving updates.
Fair enough. Filed bug 1106209.
Note: I'm not saying that this should be used for this case since not working for these users should be sufficient but there is also the capability to notify the user that their version is no longer supported (see bug 886543).
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.