Google Chrome Stable Release

broken image


Last week, it was announced that Google would be pausing its standard update schedule for Chrome and Chrome OS, instead keeping version 80 running well with bug and security fixes. Now we're learning that, due to these delays, there won't even be a version 82 of Chrome or Chrome OS.

Hide Blink components. Discuss File an issue Privacy About File an issue Privacy About. 2 days ago  Google is planning to speed up Chrome releases later this year. Chrome will move to a four week schedule, instead of six weeks. A new Extended Stable channel will also be available for IT admins. You must wait for Google to renew their keys and for an update. The important message is: The following signatures were invalid: EXPKEYSIG 1397BC53640DB551 Google Inc. (Linux Packages Signing Authority).

Before the release schedule push was announced, we were expecting Chrome and Chrome OS version 81 to begin releasing soon. As that version has already reached the beta phase, we're expecting Google will launch Chrome 81 once they feel confident in releasing despite their employees 'adjusted work schedules' or once we've properly beaten the coronavirus and gotten back to work.

After that, one would expect the version after Chrome 81 to be Chrome 82, but that doesn't seem to be the case, according to an announcement spotted by Chrome Unboxed in the official Chromium Google Group. Instead, the announcement states that Chrome 82 is being skipped altogether, emphasis theirs.

Google Chrome Enterprise Stable Release

As we adapt our future milestone schedules to the current change in schedule, we have decided to skip the M82 release to ensure we keep users safe and focus all efforts on maintaining stability.

To that end, it looks like Google is abandoning the work done to get Chrome 82 stable in preparation for it to be released. From there, Chrome 83 will become the version that those of us on Dev and Canary release channels will use.

Here are some of the immediate actions based on the above decision:

  • We will abandon current M82 branches, remove infra support, and stop testing/merges to the branches
  • We will not push any new M82 releases to Dev, and we will stop stabilization for Beta
  • We will move Dev channel to M83 asap
  • We will keep Beta channel on M81 until M83 is ready to be promoted

Essentially, the features that would have launched in Chrome 82 will be held until Chrome 83, which should make for an exciting update once we get on the other side of this crisis. Once Google is able to release Chrome and Chrome OS 81 sometime later this year, only then will the company begin to make a decision on when to set Chrome 83's projected release date and resume Chrome's release cycle.

Once M81 is cleared to release to Stable, we expect to adjust our future milestone schedules, including possibility shifting M83 forward to target an earlier branch and Stable date.

As the new Microsoft Edge is closely following Google's Chromium release schedule and version numbering scheme, even pausing their own updates when Google paused Chromium's, it's likely that Edge will also skip version 82.

More on Chrome:

FTC: We use income earning auto affiliate links.More.

Google chrome stable release schedule

Later this year, we plan to shorten the release cycle and ship a new version of Google Chrome to the stable channel every four weeks, down from the current six-week cycle. There's more detail on the Chromium Blog about the impetus and rationale for this change. Download a page chrome.

Google Chrome Stable Release

Later this year, we plan to shorten the release cycle and ship a new version of Google Chrome to the stable channel every four weeks, down from the current six-week cycle. There's more detail on the Chromium Blog about the impetus and rationale for this change. Download a page chrome.

One of my favorite aspects of being a web developer is the ease of deployment. I can fix a critical bug and deploy it to all of my users quickly. Moving to a four-week release cycle will give us more agility to get critical security and bug fixes out to users faster. And for developers, you won't have to wait as long for updates and bug fixes.

Shifting to a faster release cycle allows us to experiment and iterate on new features more effectively via origin trials, without having to wait as long between releases. It doesn't mean we'll be shipping more features, or shipping new features in less time. Google chrome 40. And it doesn't change the way we ship new features. We remain committed to working with standards bodies, our developer community, and the Chromium ecosystem.

Timeline #

Our current plan is for Chrome 94 to be the first release on the new four-week schedule, and it will be released on September 21st, 2021 (instead of October 12th, 2021). Each subsequent release will take place four weeks later. Thus, Chrome 93 (August 31st, 2021) will be the last release on the six-week schedule. We've updated our release calendar so you can see the updated dates.

As always, this may change based on feedback we receive from our team and the developer community.

What channel should I be using? #

As a web developer, it's a good idea to have both stable and beta installed on your device, and test your site in both. By using the beta channel, you can find and fix any issues before the majority of your users see them. With the beta channel you can start using new DevTools features sooner, and get early access to new web platform features. Side-by-side installation of the different channels of Chrome is available on all platforms, including Mac.

Today, it can take upwards of 2 weeks for the majority of users to move to the latest stable release. We believe that the four-week release cycle will allow us to more consistently move the majority of users to the latest stable release within 2 weeks. Of course, it's always a good idea to check the analytics for your site to understand how fast your users upgrade to the latest stable. In some scenarios, it may be longer.

How can I stay up to date? #

For web developers, there are several ways to stay informed about the things you care about.

Chrome Stable Windows 10

  • Beta posts on the Chromium blog: Highlights new web platform features that are landing in the latest beta release.
  • New in Chrome: Highlights new web platform features that landed in the latest stable release.
  • New in Chrome DevTools: Highlights new features in Chrome DevTools.

Supporting developers #

Download Google Chrome Stable Version

We've tried to make sure that the impact of this change is minimal to web developers, but there are some things that we may have overlooked. We'll keep this post up-to-date as we progress. If you have questions, or concerns, reach out to @ChromiumDev on Twitter with the hashtag #ChromeFaster.

We know this is a big change, but we feel strongly that it's something that will benefit everyone by reducing the time it takes to get important updates, and will improve the overall quality of Chrome.

Google Chrome Stable Release Tool

Hero photo by Marc-Olivier Jodoin on Unsplash.





broken image