The AchieVer Posted May 9, 2019 Share Posted May 9, 2019 Mozilla Delays Firefox 67 Launch Following Certificate Issue The certificate issue that disabled Firefox extensions last week keeps giving headaches to Mozilla, and after the company released two different browser updates to resolve the problem, it’s now coming back with another important change. Firefox 67, which is the next major release of the browser, will be delayed for one week, so instead of May 14, it’s now expected to land on May 21. In a newsletter linked by TechDows, Ritu Kothari, TPM Lead at Mozilla, explains the delay impacts all the other builds of Firefox. As such, the Feature Complete milestone for Firefox 67 has been pushed from May 3 to May 10, while the Nightly Soft Code freeze is now scheduled to take place on May 13, the same day when the first merge should be completed (after originally due on May 6). Update fatigue The newsletter also suggest that the number of patches released by Mozilla could cause what is being described as update fatigue for users. “Might be experiencing update fatigue (hotfixes and dot releases pushed in quick succession). We need time to let the dust settle on release channel owing to recent dot releases,” Mozilla’s engineers explain regarding the delayed launch of Firefox 67. “Typically, we require a week of code freeze and RC builds to ensure the release going out the door is meeting the high standards of quality, stability, and performance.” Firefox 68, which is the next-next major update for Mozilla’s browser, is not affected by this change of dates, and it should still land on July 9 as originally planned. The most recent update for Firefox is version 66.0.5, which shipped earlier this week specifically to implement more fixes for the certificate problem. According to the aforementioned schedule, no other updates for the stable version of Firefox would go live by the time Firefox 67 lands on May 21. Source Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.