{"id":163101,"date":"2026-03-04T11:11:54","date_gmt":"2026-03-04T09:11:54","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/chrome-perehodit-na-dvuhnedelnyj-czikl-podgotovki-relizov"},"modified":"2026-03-04T11:11:54","modified_gmt":"2026-03-04T09:11:54","slug":"chrome-perehodit-na-dvuhnedelnyj-czikl-podgotovki-relizov","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/chrome-perehodit-na-dvuhnedelnyj-czikl-podgotovki-relizov","title":{"rendered":"Chrome is shifting to a bi-weekly release preparation cycle.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
Google has announced a reduction in the Chrome browser development cycle by half. According to the new schedule, releases will start coming out every two weeks, rather than once every four weeks, as was practiced since 2021. Extended Stable builds, aimed at those who need more time to update, will continue to be produced every eight weeks, as before. <\/p>\n
The goal of reducing the development cycle is to deliver new features, bug fixes, and optimizations to web application users and developers more quickly. It is expected that more frequent release publications will not affect quality, will reduce upgrade failure risks, and will simplify debugging, as each release will involve fewer changes. <\/p>\n
The shortened development cycle will take effect on September 8, following the release of Chrome 153 on the old schedule. Subsequent stable releases and beta versions, which stabilize before the release, will begin to be published every two weeks. The development cycles for the Dev and Canary branches will remain unchanged, meaning that the pace of developing new functionality will continue as before, with daily Canary builds and the formation of dev builds, which undergo automated testing, produced 1-2 times a week. \n Source: opennet.ru<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"