{"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\/nl\/blog\/news\/firefox-perehodit-na-dvuhnedelnyj-czikl-podgotovki-relizov","title":{"rendered":"Firefox schakelt over op een tweewekelijkse releasecyclus","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
Sylvestre Ledru, directeur engineering bij Mozilla, heeft de overstap aangekondigd naar een tweewekelijks releasecyclus voor Firefox. Vanaf september zullen de nieuwe versies elke twee weken worden uitgebracht in plaats van eens per vier weken. Deze wijziging is al zichtbaar in de releasekalender: de laatste versie met een vierwekelijkse ontwikkelingscyclus zal Firefox 154 zijn, gepland voor 18 augustus. Daarna zal Firefox 155 op 1 september uitkomen, gevolgd door Firefox 156 op 15 september en Firefox 157 op 29 september. <\/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 workload on developers before releases. During development, a more lenient approach can be taken towards finalizing unfinished features, allowing work to progress at a realistic pace without imposing deadlines. The effectiveness of the shortened development cycle will be closely monitored and adjusted as necessary. <\/p>\n
In March, Google announced a shift to a bi-weekly development cycle for Chrome, while not changing the publication cycle for Extended Stable builds (every 8 weeks), Dev (1-2 times a week), and Canary (daily). The shortened development cycle for Chrome will take effect on September 8, after the release of Chrome 153 on the old schedule. The goal of shortening the Chrome development cycle is to publish new features, bug fixes, and optimizations faster. It is expected that more frequent releases will not affect quality, reduce the risk of issues during updates, and simplify debugging, as each release will include fewer changes. \n Bron: opennet.ru<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"