Closed Bug 1003270 Opened 6 years ago Closed 4 years ago

Drop support for 10.6.0 - 10.6.2 (free upgrade path to 10.6.3+)

Categories

(Core :: Widget: Cocoa, defect)

x86
macOS
defect
Not set

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: BenWa, Unassigned)

References

Details

(Whiteboard: tpi:-)

+++ This bug was initially created as a clone of Bug #1002857 +++

Supporting 10.6.2 is a small but non trivial burden for GFX that is slowing us down because it's one of our remaining segment that can't get OGL Layers acceleration and needs special work around. We should confirm what the real market share of 10.6.0 - 10.6.2 is and consider dropping support.
CC'ing Josh for feedback on dropping 10.6.2. CC'ing Gavin who knows which UX people to involve with this.
Flags: needinfo?(joshmoz)
Flags: needinfo?(gavin.sharp)
Flags: needinfo?(gavin.sharp)
Should we all agree to drop support here:
- Is a relnote sufficient?
- Should be have a start-up popup guiding users to run system upgrades?
- Should we disable silent update to these users?
> We should confirm what the real market share of 10.6.0 - 10.6.2 is and consider dropping support.

Metrics has already made us a chart (updated periodically) of all Mac FF users by major version since 2012-01-01 (though unfortunately it's not publicly accessible -- see bug 930325).  Presumably metrics would need to make us another, similar one containing this information.

Note that until recently we had more Mac users on OS X 10.6.X than on any other major version.  And even now OS X 10.9.X is only just ahead of 10.6.X.  But I suspect the number of users on 10.6 - 10.6.2 is much smaller.
(In reply to Benoit Girard (:BenWa) from comment #2)

I don't have access to a graph that shows 10.6.0-10.6.2 OS X usage within all 10.6 users, but it's probably quite small. I'm probably fine dropping support, though I wish we had numbers. I'm sure we could get them but the question is whether it is worth it or not. Resources spent on this are taken away from something else.

> Should we all agree to drop support here:
> - Is a relnote sufficient?

We should have a relnote, but also make sure we don't upgrade < 10.6.3 users

> - Should be have a start-up popup guiding users to run system upgrades?

Probably not worth it.

> - Should we disable silent update to these users?

Yes
Flags: needinfo?(joshmoz)
Bjacob has 300,000 crash reports we use to get statistics in GFX. For those 8 were of the relevant range. That's 0.002%. But let's confirm with our other metrics.
(Following up comment #3)

> Metrics has already made us a chart (updated periodically) of all
> Mac FF users by major version since 2012-01-01 (though unfortunately
> it's not publicly accessible -- see bug 930325).

I should have said bug 930235.
Robert, do we have existing updater UI support for showing a "please update your OS" message?
Flags: needinfo?(robert.strong.bugs)
The client side was implemented in bug 843497 and the server side has yet to be implemented in bug 886543.
Flags: needinfo?(robert.strong.bugs)
I suspect that the version reported system-info isn't going to be enough to accomplish this just as it wasn't for Windows. :(
http://mxr.mozilla.org/mozilla-central/source/toolkit/mozapps/update/nsUpdateService.js#321
For the release notes, any idea when 10.6.{0,1,2} won't have support?
(I fixed it to use the correct tag)
relnote-firefox: --- → ?
Keywords: relnote
Once we land a patch to disable silent update to these users I think.
Please set again the relnotes flags when the patch has landed.
relnote-firefox: ? → ---
Benoit, did we ever land the patch breaking 10.6.2?
No. That would be bug 1002857 which is blocked by this. Sounds like doing all this work to support dropping a minor version is more than we would gain by breaking it so I haven't really pushed for it.
Whiteboard: tpi:?
See https://hg.mozilla.org/mozilla-central/rev/0d34cec0093a. See alo bug 1255589 and dependent bugs for more info.
Based on that, this probably won't be addressed, even for ESR.
Whiteboard: tpi:? → tpi:-
Yeah, resolving this as WFM.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.