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). This proposal addresses implementation and, if adopted, would affect organizations who deploy the ESR AND allow Firefox to update through its built-in updater.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |