#WHAT IS CURRENT VERSION OF FIREFOX UPDATE#
#WHAT IS CURRENT VERSION OF FIREFOX ARCHIVE#

Organizations that rely on Firefox's built-in updater may be limited to a transition period of 6 weeks, dependant upon how the ESR releases are maintained. have disabled automated updates) to Firefox to qualify and test against Aurora and Beta builds for twelve weeks leading up to the ESR, and an additional 12 weeks to certify and transition to a new ESR. This will allow organizations who control updates (e.g. To permit organizations sufficient time for testing and certification, the ESR will have a two cycle (12 week) overlap between the time of a new release and the end-of-life of the previous release. Releases will be initially maintained for nine release cycles (currently 54 weeks, which is close to the target of 52 weeks the proposal is attempting to hit), with point releases coinciding with regular Firefox releases. Mozilla will offer an Extended Support Release (ESR) based on an official release of Desktop Firefox. To our knowledge, most organizations that deploy the ESR would disable automatic updates, and this should not affect them.

It does not affect the intent of the ESR proposal itself, but could limit the deployment time organizations that deploy the ESR and use Firefox's built-in updater to one release cycle (6 weeks).

#WHAT IS CURRENT VERSION OF FIREFOX UPDATE#

This proposal addresses implementation and, if adopted, would affect organizations who deploy the ESR AND allow Firefox to update through its built-in updater.

John O'Duinn has posted a proposal for maintaining the ESR from a Release Engineering point of view.

Product enhancements, such as Microsoft Scriptable Installer (MSI) and Group Policy Object (GPO) support are not part of this proposal.

A Thunderbird-specific discussion is held on the Thunderbird Enterprise mailing list, and is documented here

The proposal doesn't address organizations deploying Thunderbird.

This is a proposal for an Extended Support Release (ESR) for Firefox that will help meet those needs. These groups - which include small & medium business, enterprise, academic, and government - want to continue to offer Mozilla products to their users, but they need a version of Firefox that gives them a longer support tail than what we currently offer.

the associated end-of-life policy exposes them to considerable security risk if they remain on a non-current version past Firefox 3.6.

The release schedule doesn't allow sufficient time for the organizations and their vendors to certify new releases of the products.

The shift to a new release process has been difficult for organizations that deploy Firefox to their users in a managed environment.

6 Additional Information (please review).

Note: This proposal has been accepted and implemented via bug 717106. At some point down the road we might need to reclaim the resources ESR uses, perhaps turn over the build generation to community, or other issues with backporting security fixes might become blockers that result in this branch being to rest.ДЇor now, we'll continue the cadence and structure that has worked for the past 2+ years. As such there is no plan at this time to end ESR releases, the next ESR version will be 31 and each subsequent one will be 7 version numbers higher. However as we've gotten more streamlined about supporting the ESR releases alongside mainline Firefox it's become fairly trivial to keep this branch running and with the mailing list becoming community-driven, even more so. Update The original plan for ESR was to do 3 extended support releases and then potentially EOL that branch and its associated resources.

#WHAT IS CURRENT VERSION OF FIREFOX ARCHIVE#

This is an archive of the process by which the ESR channel & builds were created, it's not kept up to date with more information, for that go HERE.

What is current version of firefox