Closed
Bug 1319444
Opened 8 years ago
Closed 7 years ago
Stop advertising Firefox updates to 32-bit Linux clients with SSE on the release channel
Categories
(Release Engineering :: Release Requests, defect, P3)
Tracking
(firefox53blocking fixed)
RESOLVED
FIXED
People
(Reporter: rail, Unassigned)
References
Details
(Whiteboard: [releaseduty])
+++ This bug was initially created as a clone of Bug #1319442 +++ +++ This bug was initially created as a clone of Bug #1308167 +++ We need to setup SSE desupport rules on the release channel before we ship 53.0 RC1, see bug 1308167.
Reporter | ||
Updated•7 years ago
|
Priority: -- → P3
Updated•7 years ago
|
status-firefox53:
--- → affected
tracking-firefox53:
--- → +
Comment 1•7 years ago
|
||
Marking this a release blocker now that we're in beta - just so we remember to do it before RC.
Comment 2•7 years ago
|
||
We don't have a sumo page to point to the desupport notice to. I wonder if https://support.mozilla.org/kb/your-hardware-no-longer-supported can be fixed so show content for Windows deprecating SSE in 49 and Linux 32 in 53.
Comment 3•7 years ago
|
||
Actually, that's incorrect. That url turns into https://support.mozilla.org/t5/Install-and-Update/Your-hardware-is-no-longer-supported/ta-p/39389 in the new sumo, which has correct info for Windows and Linux. #build says we only support Macs with SSE2-capable CPUs via our 10.9 requirement, so the 49.0 text on sumo matches that too.
Reporter | ||
Comment 5•7 years ago
|
||
I think we are handling this issue this week.
Flags: needinfo?(rail) → needinfo?(jlorenzo)
Whiteboard: [releaseduty]
Comment 6•7 years ago
|
||
This should be done now. like beta[1], linux 32-bit users with SSE should receive most recent release version prior to 53.0. first Firefox-52.0.2-build1: https://aus4-admin.mozilla.org/rules/573 then SSE-desupport page: https://aus4-admin.mozilla.org/rules/574 [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1319442
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Updated•7 years ago
|
Flags: needinfo?(jlorenzo)
Updated•7 years ago
|
Comment 7•7 years ago
|
||
It looks like this was not set-up correctly. The first rule should've been a watershed - because <52.0 don't send instructionSet at all. It also looks like the blob that the desupport rule points at (SSE-Desupport) has the wrong version set (48.0) - so it never returns the desupport notice. This is probably because that blob was previously used as the desupport blob for Windows, where we desupported SSE earlier. We should've used a new blob with a different version set for Linux.
You need to log in
before you can comment on or make changes to this bug.
Description
•