This is the Linux analog of bug 1271762. At some point, Mozilla-provided builds for 32-bit x86 Linux will stop working on CPUs that don't support the SSE2 instruction set extension. At that point, the update server should no longer offer updates to 32-bit x86 Linux clients that don't have SSE2 and should point those clients to a SUMO article instead. * Which version of Firefox will require SSE2 on 32-bit x86 Linux is still unclear: bug 1274196. * The update client on Linux does not communicate SSE2 availability to the server yet: bug 1277359. * It's unclear to me if a new SUMO article should be created or if the existing one should be amended with Linux-specific information. The existing article is https://support.mozilla.org/en-US/kb/your-hardware-no-longer-supported . Linux-specific information should include a mention to the effect of "You may be able to obtain a version that does not require SSE2 from your Linux distribution."

I suggest having the following rules: * 50 or earlier update to 52. * 51 and 52 update to latest release if SSE2 is present. * 51 updates to 52 if SSE2 is absent. * 52 shows a link to a tombstone SUMO article if SSE2 is absent.

Can I rephrase the above as: * SSE detection code is available in 51 the earliest * 53+ is where SSE is desupported Does it sound correct?

(In reply to Rail Aliiev [:rail] ⌚️ET from comment #2) > Can I rephrase the above as: > > * SSE detection code is available in 51 the earliest > * 53+ is where SSE is desupported > > Does it sound correct? Correct.

I filed 2 bugs to handle this for beta and release. Let's use this one as a tracking bug.

Should I land bug 1274196 now or wait for a Balrog config change?

I created a rule to point Linux+SSE users to the 20161126030207 nightly. Feel free to land the patch any time.

Thank you. I landed bug 1274196.

(In reply to Henri Sivonen (:hsivonen) from comment #0) > * It's unclear to me if a new SUMO article should be created or if the > existing one should be amended with Linux-specific information. The existing > article is > https://support.mozilla.org/en-US/kb/your-hardware-no-longer-supported . > Linux-specific information should include a mention to the effect of "You > may be able to obtain a version that does not require SSE2 from your Linux > distribution." I contributed Linux-specific text to the existing SUMO article. It's still pending review: https://support.mozilla.org/en-US/kb/your-hardware-no-longer-supported/history#preview

Tracking this for 52 and 53 so relman can be aware and to make sure we have all the pieces in place.

I created a staging/test aurora equivalent of the nightly balrog rule in comment 6: https://aus4-admin.mozilla.org/rules/492 This just needs a channel name update to 'aurora*' and a more update buildid once we are ready to desupport in aurora. Do we want to put this in place before the first 53.0 aurora nightly? i.e. using the buildid that will be used when we freeze aurora updates during merge week?

fyi, further changes I've made: with m-c nightlies: added "Build ID: <20161126030207" to: https://aus4-admin.mozilla.org/rules/477 duped rule 477 then made mapped it to No-Update: https://aus4-admin.mozilla.org/rules/493 with m-a auroras: duped staging rule 492 then made mapped it to No-Update: https://aus4-admin.mozilla.org/rules/494

aurora is done now: https://bugzilla.mozilla.org/show_bug.cgi?id=1320497#c1

Should this be marked resolved? Or is there more left to do for 52 as well?

thanks for the sanity check. this bug tracks all the trains. We still have beta and release to deal with as it rides: bugs 1319442 1319444

This is done for 52 now and I think we can drop tracking for 53 since I'm already tracking it for release 53 in bug 1319444.

Should this now be FIXED, or is there something to do?

yes I believe this is done and can be resolved.