Firefox ESR release cycle

Firefox for Enterprise Firefox for Enterprise Last updated: 08/05/2021 49% of users voted this helpful
아직 누구도 이 문서의 번역에 참여하지 않았습니다. SUMO 문서 변역에 참여하는 방법에 대해 이미 알고 계시다면, 번역을 시작해 보세요 . SUMO 문서를 번역하는 방법에 대해 알고 싶으시면, 여기서 시작하세요.

Overview

Firefox offers an Extended Support Release (ESR) for organizations, including schools, universities, businesses and others who need extended support for mass deployments. Firefox ESR can be downloaded here. The ESR release is based on the regular release cycle of Firefox for desktop.

Release cycle details

ESR releases are maintained for more than a year, with point releases that coincide with regular Firefox releases. These point releases contain security upgrades.

The ESR version will also have a three cycle (at least 12 weeks) overlap between the time of a new release and the end-of-life of the previous release to permit testing and certification before you deploy the new version to your organization.

We rely on Firefox ESR users to provide feedback for each new ESR release. During the first two cycles, please report any bugs such as web compatibility regressions and stability issues.

Maintenance of each ESR through point releases is limited to high-risk/high-impact security vulnerabilities, and in rare cases may also include off-schedule releases that address live security vulnerabilities. Backports of any functional enhancements and/or stability fixes are not in scope.

At the end of the support period for an ESR version:

  • the release will reach its end-of-life
  • no further updates will be offered for that version
  • an update to the next version will be offered through the application update service

ESR Release Cycle

You can read more about the ESR landing process here.

Upgrade path between two ESR versions

An ESR release will be automatically upgraded to the subsequent ESR release. System administrators can disable automatic updates by managing ESR through their deployment system. From one major version to another, such as the version 52 to version 60 migration, the updates will be implemented only after version X.2.0 is released. For example, users of version 52 will be updated only when version 60.2.0 has been published.

이 문서가 도움이 되셨습니까?

잠시만 기다려 주십시오...

문서 작성 및 변경에 도움 주신 분들

Illustration of hands

도움 주기

전문 지식을 성장시키고 다른 사람들과 공유세요. 질문에 답하고 지식 기반을 개선할 수 있습니다.

자세히 살펴보기