(from :lsblakk's email) We're approaching the time window where we'll be offering two versions of Firefox ESR at the same time overlapping so that means https://www.mozilla.org/en-US/firefox/organizations/all.html needs to reflect both ESR17 and ESR24 download links for all locales. We'll basically have the following two ESR releases for the next set of release dates (and will need to update http://viewvc.svn.mozilla.org/vc/libs/product-details/firefoxDetails.class.php?view=markup accordingly): 9/17 - release 17.0.9esr, 24.0esr (24.0esr matches 24.0 general audience release) 11/29 - release 17.0.10esr, 24.1esr 1/21 - release 17.0.11esr, 24.2esr (ESR17 gets EOL'd here) 3/4 - release 24.3esr (only 24.3esr links on the download webpage and in firefoxDetails.class.php)

Do we know how exactly firefoxDetails.class.php will change? I only see one spot for the latest ESR version number. Will there be another constant added? e.g.: define('FIREFOX_ESR', '24.0esr'); define('FIREFOX_PREV_ESR', '17.0.8esr');

As discussed in IRC, for today's release I've hardcoded the 24.0esr table into the production all.html page which buys us 6 weeks to either port this to bedrock or figure out how to add in a second ESR release version to the current system. I believe there is a preference for bedrock porting :) See http://viewvc.svn.mozilla.org/vc/projects/mozilla.com/tags/production/en-US/firefox/organizations/all.html?view=log for changes (hardcoding)

Tracking this since we'll want to be able to use the product-details to update the page next release (in 4 weeks) instead of hardcoding the table for esr24 release into the all.html page.

I'll be meeting with webprod team tomorrow to discuss porting product-details over to bedrock which should help us get a timeline for this.

Hi Lukas, Just checking in. Are we still moving forward with using product-details and porting this to Bedrock? Do we need to regroup?

We're about to EOL FF17esr on December 10th so we will return to having only one version for esr (24) in the product-details. The next esr version will be FF31 and that will be over a year from now. It's my understanding that by the time this version rolls around, we will no longer be relying on product-details like we do now and will instead be using Nucleus to publish notes and version download updates. We probably can push this bug into the meta tracking for Nucleus to remember that it's needed in that process.

Not tracking this for FF26 since that's not logical given the above comment re: EOL of ESR

Firefox 31, the next ESR, is already Aurora.

Justin, Mike - it's 6 weeks now until we ship FF31 and will need to process two versions of ESR in parallel on the org page. Can we get this triaged & prioritized so Bedrock will be able to serve these pages by then based on product-details (and, presumably, a second ESR value in p-d)?

(In reply to Lukas Blakk [:lsblakk] from comment #10) > Justin, Mike - it's 6 weeks now until we ship FF31 and will need to process > two versions of ESR in parallel on the org page. Can we get this triaged & > prioritized so Bedrock will be able to serve these pages by then based on > product-details (and, presumably, a second ESR value in p-d)? Lukas, we're all set for serving the 2 ESR releases tmrw. Details in bug#1022900. Is there a time of day this should go live?

We typically push the ESR around 10am PT.

Marking this old one resolved