Extended Stable now bundles four Chrome milestones into the same eight-week window

The admin who pulls Chrome 153 into a test image this week is certifying a browser whose successor is already in beta ^[4]. That is the practical shape of the change: 14 days from a milestone reaching Stable to the next one landing ^[12], and 26 of those a year where there used to be 13 ^[15].

One line in Google's pitch is meant as reassurance, though it functions more as a warning. Smaller scope per release makes regression isolation faster ^[11]. That is true, and it is also the argument against the enterprise channel, because scope per release is precisely what Extended Stable now accumulates.

Extended Stable kept its calendar, which is where the arithmetic bites. It still steps every eight weeks, but eight weeks now spans four milestones instead of two: 9to5Google lists Chrome 156 followed by Chrome 160 ^[5], where the same gap under the four-week cadence covered two version numbers ^[14]. The dates on the wall are the same. But each jump now carries twice the web-platform delta, and isolating a regression means checking across four milestones of change instead of two.

The security case for moving everyone onto Stable does not hold up as well as it sounds. Google's stated aim, per TechCrunch, is keeping the N-day gap small, meaning the interval between a vulnerability being known and the fix reaching users ^[16], and it says patch volume has risen as automated tooling and community bug reports surface more of them ^[10]. Engadget reports that Extended Stable still ships security fixes weekly, holding only major feature updates to the two-month rhythm ^[6]. The reason to leave Extended Stable, then, is feature and interoperability drift, not patch exposure. Google's guidance skips that distinction and says most enterprise users belong on the two-week Stable channel ^[9].

What none of the coverage supplies is the other half of the equation: how long enterprise certification actually takes, or how many managed fleets sit on Extended Stable today. "Most enterprise users should be on Stable" is advice, not a measurement ^[9].

The number that decides it is your own median time from a milestone hitting Stable to the last business-critical app being confirmed working. Under 14 days, Stable was always fine and remains fine. Between 14 and 56 days, you are choosing the shape of your failures rather than avoiding them: small breakages often on Stable, against a four-milestone cliff on a date you can put in a diary ^[13]. Over 56 days, no channel Google offers matches your process, and the honest conclusion is that your users have been running whatever Chrome shipped, tested or not.