There is a misunderstanding in this BZ that Enterprise customers would wait for FF24 ESR to go EOL before starting their migration to FF 31 ESR.   We purposefully worked with Mozilla Development when the Extended Support Release was proposed to create an overlap of two release cycles.    As a result, Firefox 31 ESR becomes available two cycles before Firefox 24 ESR goes EOL.   Enterprises uses these 12 weeks to migrate hundreds of thousands of systems to the next ESR before the prior release goes out of support.  We don't want our desktop systems to be running on unsupported (and potentially vulnerable) releases of the older Firefox ESR.   During the transition both ESR releases are secured by backports of security errata.  After a Firefox ESR goes EOL, Mozilla continues to publish security errata (at least every 6 weeks) that could disclose security vulnerabilities in prior releases.   Those open source disclosures could tip off hackers on how to attack prior releases of Firefox.  This would put enterprises at risk, if they don't stay vigilant and current with their browser policy.

We are going to provide Firefox 31 ESR rpm packages as soon as possible for testing purposes. So the customers can test their scenarios during the overlapping period and report issues to us.

Thanks Martin! That works much better for us.

To be clear here, Firefox team is going to provide test packages based on official Mozilla Firefox 31 ESR packages. So you can expect those packages after July 22 which is current release date by Mozilla.

Great - Thanks for the clarification that the Red Hat test packages will be built from the official Firefox 31 ESR packages (after July 22)