The Chrome browser differs from Chromium in its use of the Google logos
Google unveiled via a blog post, their plans to make a change to the release cycle model for your Chrome web browser, for a shorter one.
Google mentions that the purpose of making the change is to reduce the time between creating a new branch and starting beta testing, in which the beta version will be created two days after the branch is created, instead of the current model which is 8 days.
The beta will continue to stabilize for 4 weeks. Thus, the preparation cycle for a new release will be one week shorter.
Regarding this new model that is planned to be adopted in Chrome, it is worth mentioning that is something similar to recent cycle of updates that Canonical implemented in Ubuntu (I don't know at the moment if they were inspired or taken as a basis). And it is that he Canonical model 4/2, this seeks to be able to address the correction of vulnerabilities in a shorter period.
Since as you mentioned, Canonical's new 4/2 model is based on the fact that two weeks after the start of the generation cycle of the next SRU (Stable Release Updates), a separate SU update will be published, which includes fixes only for dangerous vulnerabilities and important issues.
For example, in the case of the new Chrome model, taking the Chrome 119 branch as an example, it is mentioned that with the previous model the launch of this version would be expected on October 3, but with the new model it will arrive on October 2, while for the release of the beta version instead of being released on October 11 (previous model), it would be being released on October 4 (just three days after the release of the stable version and as for the next stable release which would be Chrome 120, instead of arriving on November 7, it would be launching on October 31.
Furthermore, it is also mentioned that The generation cycle of intermediate updates with vulnerabilities has recently been shortened, With which it is expected that the change will benefit when testing corrections and discovering errors. Although it is also mentioned that one of the negative points of the change is that the Hackers can take advantage of the visibility of these fixes and develop exploits to apply against browser users who have not yet received the fix (this exploitation of a known and patched security issue is known as an n-day exploit).
Chrome ships a new major version every four weeks. Between those major releases, we ship updates to fix security bugs and other high-impact bugs. We currently schedule one of these stable channel updates (or "Stable Update") between each milestone. Starting with Chrome 116, stable updates will be released every week between milestones.
And, if previously, within the 4-week cycle of creating a new major version, corrective updates were published two weeks after the next version, starting with Chrome 116, these updates began to be formed every week in the presence of vulnerabilities . In the case of eliminating critical or already exploited vulnerabilities, as before, the update will be released out of schedule.
It is worth mentioning that for those interested in knowing the Chrome roadmap, you can consult it from the following link, while to check the Chromium release schedule, you can consult the information this link.
As a personal comment, I can say that trying to address security issues and bug fixes in shorter times is an extremely good thing for users, but further shortening the stable release cycle can lead to some type of conflict with users, in addition to the fact that the new releases, in most cases, could merely be corrections and some improvements and would no longer be presenting new features or additions in functionality as was previously done.
Finally if you are interested in knowing more about it, you can check the details in the following link