Google Speeds Up Chrome Updates
▼ Summary
– Google is shortening Chrome’s release cycle to two weeks, starting in September with version 153.
– This change aims to deliver performance improvements, fixes, and new features to users and developers more quickly.
– The faster, smaller releases are also intended to simplify the debugging process for developers.
– The new two-week cycle applies to the stable and beta versions of Chrome on desktop, Android, and iOS.
– The Dev, Canary, and Extended Stable channels for enterprise will maintain their existing, longer release cycles.
Google is accelerating the pace of its Chrome browser updates, shifting to a new two-week release schedule for stable versions starting in September. This marks a significant departure from the previous four-week cadence and the six-week cycle that defined the browser’s development for over ten years. The company states this adjustment is designed to deliver performance enhancements, security patches, and new features to users and developers more rapidly. By implementing smaller, more frequent updates, Google also aims to streamline the debugging process for its engineering teams.
The new schedule will debut with the stable launch of Chrome 153 on September 8th, affecting the desktop, Android, and iOS versions of the browser. The Beta channel will also adopt this accelerated two-week timeline. However, this change does not apply to all development tracks. The Dev and Canary channels, which are used for earlier testing, will maintain their existing schedules. Furthermore, the Extended Stable release option for enterprise administrators and Chromium embedders will continue on an eight-week cycle, providing the stability required for managed environments.
This strategic move reflects Google’s ongoing effort to keep pace with the dynamic demands of the modern web. Faster iteration allows the company to integrate improvements and address issues more promptly, potentially enhancing security and user experience. For the vast majority of everyday users, this transition will likely be seamless, with updates continuing to install automatically in the background. The core objective remains delivering a more responsive, secure, and capable browsing experience through a more agile development process.
(Source: The Verge)
