3 ms·
Just in case you were unaware, Firefox has extended support releases [1] for environments where rapid releases are too much hassle. This is a supported option f
by nirvdrum 7y ago
Just in case you were unaware, Firefox has extended support releases [1] for environments where rapid releases are too much hassle. This is a supported option from Mozilla whereby you get security fixes but the feature set doesn't change for 42 weeks. Which is to say that ESRs aren't some odd admin policy, but rather part of the supported Firefox line and widely used in bigger companies.
Apologies if you were aware and were talking about some other admin policy. I've run into other devs that weren't aware, so thought I'd share.
1 - https://support.mozilla.org/en-US/kb/choosing-firefox-update-channel https://support.mozilla.org/en-US/kb/choosing-firefox-update...
- btown 7y agoDoes Chrome have a similar offering?
- nirvdrum 7y agoNot that I've come across or could easily find just now. Google is the one that started the rapid release cycle in browsers and extended support for anything is out of character for the company. I'm curious to see if Edge will prove to be a Chromium-based browser with an extended support cycle.
- kevingadd 7y agoMy hope is that edgium gets ESR releases, but the way Chromium handles incremental changes means backporting security fixes is going to be very hard. One great example is that a few releases back they almost completely broke web audio for a sizable (>10%) portion of their users, but they had changed so much in that time period that it was impossible to backport a fix. Users had to wait ~6 weeks for the fix to ride the trains. Firefox having a commitment to ESR means that any changes have to be built in a way that's ESR-compatible. Since mainline Chromium has no such constraints, doing that in a fork will be tough.
- kevingadd 7y agoNo, only an option to delay updates somewhat. It's a big problem and part of why enterprise customers were so badly impacted by the RDP bug a little while ago.