It seems that browsers developed based on Chromium have basically become dominant. Although Google has already put forward a fairly long-term and stable update notice and beta testing phase for its own signature browser. But it is obvious that as the number and breadth of users are increasing year by year, the pressure on software errors is also higher than imagined. It seems that because of this relationship, Google recently thought of inserting a mechanism to ensure the Stable version before the update is officially launched – just… a bit like services such as Instagram, which will open up new features to a small number of people early. Continue reading the text of the report that Chrome will launch “Early Stable” to a small number of users one week before the official version update.
Chrome will launch “Early Stable” to a small number of users one week before the official version update to test the water temperature
Regardless of other derivative versions, Google Chrome itself already has a Canary version for experimental developers, Chrome Beta, and the official version of Chrome that will eventually arrive with the Stable update. Why does Google still want to add an “Early Stable” to the existing Beta and Stable update schedule?
According to the official statement, this will push the official version that is biased toward early preview to a small number of users one week before the stable official version of Chrome is updated. The main use is like testing the water temperature. Even if an error occurs, the scope of the disaster can be controlled within a smaller range. The point is, there is still a week to buffer before the scheduled update push time.
Therefore, this is indeed a relatively safe and responsible way to prevent the unstable Stable version from being released in large packages because it is pushed to all users at once – except for those few selected people who actually encounter problems (helping QQ).
I have to say, although it is difficult to say whether these users selected by the Early Stable update are lucky or unlucky. However, as the number of Chrome users increases, in order to find bugs that beta testers may still encounter, this is also an additional assurance mechanism. It can be regarded as another layer of defense when users actively choose to install the beta version to help eliminate bugs.
Google plans to start inserting the new Early Stable concept into the Chrome 110 version. After the beta test is completed in mid-January 2023, Early Stable will be pushed to a small number of users one week before the scheduled launch of the Stable version on February 7, that is, on February 1.
Interestingly, although the official has not announced how this list will be screened. But as Google mentioned that the number of Early Stables is determined by a “percentage”, it is not surprising that the scale of this test will also increase or decrease with the number of users – I wonder if this % number will be linked to the Stable error rate? Hmm… In this case, wouldn’t everyone be looking forward to being selected?
All I can say is that if I keep being selected, I will probably just grab the Beta and use it (just take the initiative XD).
Further reading:
Source: KOCPC Chinese