Google to Skip Chromium 82 Because of Coronavirus

Posted on March 23, 2020 by Paul Thurrott in Google Chrome, Microsoft Edge with 7 Comments

After hitting pause on Chromium 81 because of the Coronavirus pandemic, Google now says it will skip Chromium 82 as well.

“Our top objective is to keep trunk/master in a stable, reliable state,” Google engineer Jason Kersey originally wrote last week in a post to the Chromium group in Google Groups. “This means in practice we will not be promoting new milestones to stable during this period and that the scheduled release of [Chromium] 81 will stay on hold pending our decision to resume releases.”

For Chromium 82, Google originally said that it would release one more Dev channel build to gather more stability data. But that’s over, and Google is now skipping past Chromium 82 as well.

“We will abandon current [Chromium] 82 branches, remove infra support, and stop testing/merges to the branches,” Kersey wrote in a follow-up. “We will not push any new [Chromium] 82 releases to Dev, and we will stop stabilization for Beta. We will move [the] Dev channel to [Chromium] 83 ASAP. [And] we will keep the Beta channel on [Chromium] 81 until [Chromium] 83 is ready to be promoted.

What this means is that Google’s next planned release is Chromium 83, for which it will continue shipping daily Canary builds as planned. And that, in turn, will impact not just Chrome but other Chromium-based browsers as well, including Microsoft Edge.

“We expect to provide another update next week around our anticipated next steps and timing around releasing [Chromium] 81, and branching for [Chromium] 83,” Kersey continues. “Thanks again for your patience and support.”

Join the discussion!

BECOME A THURROTT MEMBER:

Don't have a login but want to join the conversation? Become a Thurrott Premium or Basic User to participate

Register
Comments (9)

9 responses to “Google to Skip Chromium 82 Because of Coronavirus”

  1. kevineddy

    Why skip a release, as opposed to delaying?

    • safesax2002

      In reply to kevineddy:

      I'm guessing they want to keep everything as stable as possible while we are all having to support teleworkers. Us IT Admins don't need anything more to take on right now.


      Now it's not a great long-term strategy but for the foreseeable short-term it's the smart play.

    • datameister

      In reply to kevineddy:


      Chrome has a Canary, Dev, Beta, and Stable channel release system. So a lot of version numbers in the chain at any given time. Maybe they figure by the time they get the whole system working again they can merge some of the testing instead of pausing the entire upper part of the chain.


      Or maybe it's the same problem they had with 81 and they still can't get it fixed.

  2. saint4eva

    Google Chrome is beginning to fall apart.

  3. arnstarr

    Skipping to two Stable releases means no release for 12 weeks.

  4. wright_is

    What I don't understand is, if they can't guarantee that 81 and 82 will be worked on reliably enough to get a release, why do they think 83 will be any different? And by current estimates, they will have to push this out to 84, 85 and probably 86 as well...

    Google has been promoting the cloud and the ability to work anywhere for at least a decade, yet they can't actually do it themselves, for their own projects? Other open source projects run with remote developers who never see each other all the time.

    The supplied information doesn't compute or, at least doesn't put Google's cloud concept in a good light.

Leave a Reply