{"id":182643,"date":"2026-07-15T04:53:44","date_gmt":"2026-07-15T02:53:44","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/firefox-perehodit-na-dvuhnedelnyj-czikl-podgotovki-relizov"},"modified":"2026-07-15T04:53:44","modified_gmt":"2026-07-15T02:53:44","slug":"firefox-perehodit-na-dvuhnedelnyj-czikl-podgotovki-relizov","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/firefox-perehodit-na-dvuhnedelnyj-czikl-podgotovki-relizov","title":{"rendered":"Firefox is transitioning to a two-week release cycle","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
Sylvestre Ledru, Engineering Director at Mozilla, announced a shift to a two-week release cycle for Firefox. Starting in September, new releases will be generated every two weeks, rather than every four weeks. This change is already reflected in the release schedule: the last version developed under the four-week cycle will be Firefox 154, set to launch on August 18. Following that, Firefox 155 will be released on September 1, Firefox 156 on September 15, and Firefox 157 on September 29. <\/p>\n
The reduction of the release cycle is presented as an experiment aimed at delivering new features to users more frequently, ensuring a more predictable release process, and reducing the burden on developers before releases. Development can afford to be more lenient with bringing unfinished features to readiness and take as much time as needed to complete work without creating deadlines. The effectiveness of the shortened development cycle will be closely monitored and adjusted if necessary. <\/p>\n
In March, Google announced the transition to a two-week development cycle for Chrome, while not changing the publication cycles for Extended Stable (every 8 weeks), Dev (1-2 times a week), and Canary (daily). The shortened Chrome development cycle will take effect on September 8, following the old schedule for releasing Chrome 153. The goal of shortening the Chrome development cycle is to publish new features, bug fixes, and optimizations more quickly. It is expected that more frequent releases will not affect quality, reduce the risk of failures during updates, and simplify debugging since each release will offer fewer changes. \n Source: opennet.ru<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"