This small percentage of users will essentially be Google’s “canary in the coal mine” for any “showstopping” issues ahead of the wide release. Google explains that the reasoning for this tweak to its release schedule is to monitor the release before it hits the general public. Our Kyle Bradshaw points out that this is most likely a larger percentage than those who have chosen to enroll in the beta release channel, or it could be that Google is simply targeting a different subset of Chrome’s user base.įor the first release, Google notes that the schedule will be as follows: A “small percentage” of general Chrome users will get the update a week early. This won’t be a new opt-in release channel but rather a release schedule that will affect those enrolled in the stable update channel. This pushes the stable release of Chrome 110 back to February 7, 2023, instead of the planned February 1. Starting with Chrome 110, Google will expand that release schedule to include a new “early stable” release, which pushes the latest version of Chrome to users a week ahead of the full launch. As it stands today, new versions of Chrome are released first to the “canary” channel before propagating down to the dev, beta, and finally stable release channels, all of which users are able to opt into. Hero photo by Marc-Olivier Jodoin on Unsplash.Starting in February 2023, Google Chrome will change up its release cycle slightly with a new “early stable” release designed to catch major issues before they hit all users.Īnnounced in a blog post today, Google Chrome v110 will be the first version of the world’s most popular browser to switch to a new release schedule. 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. If you have questions, or concerns, reach out to on Twitter with the hashtag #ChromeFaster. We'll keep this post up-to-date as we progress. 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. New in Chrome DevTools: Highlights new features in Chrome DevTools.New in Chrome: Highlights new web platform features that landed in the latest stable release.Beta posts on the Chromium blog: Highlights new web platform features that are landing in the latest beta release.# How can I stay up to date?įor web developers, there are several ways to stay informed about the things you care about. 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. 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. Today, it can take upwards of 2 weeks for the majority of users to move to the latest stable release. Side-by-side installation of the different channels of Chrome is available on all platforms, including Mac. With the beta channel you can start using new DevTools features sooner, and get early access to new web platform features. By using the beta channel, you can find and fix any issues before the majority of your users see them. # What channel should I be using?Īs a web developer, it's a good idea to have both stable and beta installed on your device, and test your site in both. We've updated our release calendar so you can see the updated dates.Īs always, this may change based on feedback we receive from our team and the developer community. Thus, Chrome 93 (August 31st, 2021) will be the last release on the six-week schedule. Each subsequent release will take place four weeks later. 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). We remain committed to working with standards bodies, our developer community, and the Chromium ecosystem. And it doesn't change the way we ship new features. It doesn't mean we'll be shipping more features, or shipping new features in less time. 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. Choosing the best Chromebook for your needs and your budget can be hard to do given the multitude of models on the market today. And for developers, you won't have to wait as long for updates and bug fixes. Moving to a four-week release cycle will give us more agility to get critical security and bug fixes out to users faster. I can fix a critical bug and deploy it to all of my users quickly. One of my favorite aspects of being a web developer is the ease of deployment. There's more detail on the Chromium Blog about the impetus and rationale for this change. 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |