http://bugzilla.opensuse.org/show_bug.cgi?id=1152123 http://bugzilla.opensuse.org/show_bug.cgi?id=1152123#c3 --- Comment #3 from Wolfgang Rosenauer <wolfgang@rosenauer.org> --- (In reply to pie Lud from comment #2)
Yes I know Leap follow some old releases. I am not sure what ESR means, but what I understand is that they want things stable which is perfectly ok.
https://www.mozilla.org/en-US/firefox/enterprise/
Sorry that it might now seem I'm shooting the messenger, you, but just hear me out. The thing is with applications some common sense must used which might override some rules. For example FF had some security fixes, new features like tracking and ad blocking etc. ANY security fix should override this ESR rule ALWAYS and to block new or bleeding features or bug fixes not allowing them any merit is plainly ignorant to borderline dumb.
Mozilla's ESR release is explicitely secure because it gets all security fixes regular release also gets. There is a slight difference when it comes to security _features_ though where obviously Firefox regular might be ahead of ESR.
I have to say I have already moved two PCs away from openSUSE to Kubuntu and Neon. I'm using a proper latest FF on my PC, but slowly and surely getting tired openSUSE Leap. Please tell the Leap policy guys and enforcers that they are killing the disto with their hard rules.
So Kubuntu is updating every 6 weeks to the latest Firefox release from their official update channels? We just right now have a discussion for Tumbleweed because Mozilla wants to move to a 4 weeks release schedule and even the bleeding edge Tumbleweed people tend to want to have ESR as an option in Tumbleweed. In any case I'm doing the work anyway in the mozilla repo and there would be no real technical problem to also submit that package to Leap. But for sure we would need to give people the choice. In any case discussion like this should not be done in bugzilla but preferably on a mailing list like opensuse@opensuse.org. At least I'm open to that discussion. On the other hand using the mozilla repo is also a good alternative. You do not really get something different there. -- You are receiving this mail because: You are on the CC list for the bug.