Firefox 52 has been released on 2017-03-07. https://www.mozilla.org/en-US/firefox/52.0/releasenotes/
+1 It usually does not take so long for the maintainers to bump to the newer version. Is there something holding them up?
Unfortunately yes -- real life has put me in the middle of a rather involved audit, this is the initial commit to a new ESR series (meaning we need to get it right for a year instead of just 6 weeks), and there are still 8 bugs outstanding that need to be resolved before I can commit it.
You know, you can always release masked builds. There may be a lot of shee... people who might want to test for free any kind of behavior if needed.
(In reply to Ian Stakenvicius from comment #2) > Unfortunately yes -- real life has put me in the middle of a rather involved > audit, this is the initial commit to a new ESR series (meaning we need to > get it right for a year instead of just 6 weeks), and there are still 8 bugs > outstanding that need to be resolved before I can commit it. I did notice that Mozilla offers two kind of Firefox builds for downloading, the regular one and the ESR one. Couldn't something similar be done in Gentoo, I mean an ebuild something like firefox-esr (38, 45, 52 versions, etc.) and the regular one? In any case, thanks for your work maintaining the package!
That's what we do already -- ESRs are the stable packages, non-ESRs are the ~arch ones. This (52.0) is becoming ESR ie it's a stable candidate, which is why it needs to be treated with a bit more effort than a regular ~arch bump.
(In reply to Pablo Cholaky from comment #3) > You know, you can always release masked builds. There may be a lot of > shee... people who might want to test for free any kind of behavior if > needed. Agreed. Rather than pushing it to the gentoo repo I've bumped the work-in-progress on mozilla-overlay. I should have enough time to resolve remaining bugs and get it pushed to the main repo this weekend.
