On this page: https://www.mozilla.org/en-US/firefox/releases/ The releases 31.1.0, 31.2.0, ... are ESR releases. We should have 31.1.0esr, 31.2.0esr, etc to make that clearer. It seems that X.Y.Z with Y > 0 are ESR releases (after 3.6)

The files which should be updated are probably * bedrock/releasenotes/views.py * bedrock/firefox/templates/firefox/releases/index.html

(In reply to Sylvestre Ledru [:sylvestre] from comment #0) > > It seems that X.Y.Z with Y > 0 are ESR releases (after 3.6) There's one exception: 33.1

(In reply to Hector Zhao [:hectorz] from comment #2) > > There's one exception: 33.1 Also 10.0.*esr and 17.0.*esr use 0 as the second digit.

Indeed, my bad (and I was the release manager for this release ... shame on me). Thanks!

Yes, the code is here: https://github.com/mozilla/bedrock/blob/master/bedrock/releasenotes/views.py#L169 But we cannot distinguish ESR from the release channels so far: http://viewvc.svn.mozilla.org/vc/libs/product-details/history/firefoxHistory.class.php?limit_changes=0&view=markup Maybe Ship It can provide better data?

Yep, I think I could provide this information the future version of the product details ( bug 1083718 ). Adding a new field to the json file should be trivial and have no impact on compatibility

(In reply to Sylvestre Ledru [:sylvestre] from comment #6) > Adding a new field to the json file should be trivial and have no impact on > compatibility +1