"Building on our history of adapting our release process to match the demands of a modern web, Chrome is moving to a two-week release cycle. The goal is to give users and developers faster access to performance improvements, fixes, and new capabilities. The smaller scope of the releases should also simplify debugging."
"The change applies to desktop, Android, and iOS, and begins with the stable release of Chrome 153 on September 8th. Beta releases will also move up to a two-week cycle. There are no changes to the Dev and Canary channels, and Extended Stable for enterprise admins and Chromium embedders will continue to adhere to an eight-week cycle."
Google is transitioning Chrome to a two-week release cycle, reducing from the current four-week schedule and the six-week cycle that preceded it. This change applies to desktop, Android, and iOS versions, beginning with Chrome 153's stable release on September 8th. Beta releases will also adopt the two-week cadence. The accelerated cycle aims to provide users and developers quicker access to performance enhancements, bug fixes, and new capabilities while simplifying debugging through smaller release scopes. Dev and Canary channels remain unchanged, and Extended Stable for enterprise users continues on an eight-week cycle.
Read at The Verge
Unable to calculate read time
Collection
[
|
...
]