![]() We could release a new version of Chrome with hundreds of changes and updates, to billions of users in dozens of languages across multiple operating systems for thousands of different devices, all at once,-and cross our fingers and hope for the best. Web browsers don't work in isolation! They need to cope with the quirks of millions of websites, changing constantly, and all kinds of user behavior-expected and unexpected. Chrome engineers continue to test after Stable release, when real people start using the browser at scale. Widely-used, complex software needs robust processes and strict testing mechanisms to ensure that new features and changes to code avoid adding bugs and causing unexpected side effects. # Why does Chrome need release channels?Ĭhrome has thousands of contributors, millions of lines of code, and billions of users. User-Agent reduction explains plans to minimize the identifying browser version number information exposed in JavaScript and passively shared in the User-Agent HTTP request header. ![]() MAJOR must be updated for any backwards incompatible change.įind out more from Chromium Projects: Version Numbers. This site also provides tools to view code differences between versions.Ĭhrome version numbers have four parts:. You can check the latest versions for each Chrome release channel and platform at. You can observe how the version number changes over time for each channel. If you're curious about the version you're using, take a look at the chrome://version page. You'll sometimes see these major numbers referred to as milestones: for example, M101 or M102. For example, when this article was drafted, Chrome Stable was on version 101, Chrome Beta was 102, Chrome Dev and Chrome Canary were different versions of 103. For each channel, the version keeps the same major version number throughout one release cycle. # Channel ≠ versionĪ series of versions of Chrome is deployed within each release channel, as updates, improvements, and bug fixes are incorporated during testing. This is the Chrome channel you should consider as default and current-the channel installed by the vast majority of users. Changes and updates only make it into Stable after we perform rigorous automated testing and manual checks. This release is known by most people simply as 'Chrome'. # Chrome StableĬhrome Stable is updated every two to three weeks with minor updates and every four weeks for major releases. You can preview features still under development, and provide feedback to improve Chrome. With Chrome Beta, you have access to improvements and new features more than a month before the Stable channel gets them, with a level of reliability close to Chrome Stable. This browser is much more polished, carefully checked and tested. # Chrome BetaĬhrome Beta is updated about once a week, with major updates every four weeks. This release channel is still pretty fresh-we test it more than Canary, but you're still likely to find bugs and other glitches. # Chrome DevĬhrome Dev is released once or twice a week.Ĭhrome Dev shows what the Chrome team is working on right now. Remember that some features may never make it beyond Canary-that's what makes it useful! It's much better that a feature is tested (and potentially rejected, or reworked) in Canary with a small number of users, before the feature is implemented for general availability in Chrome Stable. By default, Canary reports crashes and usage statistics to Google (you can deactivate this feature).Ĭanary is very useful for developers and enterprise users who need to test new features as soon as they're implemented. The good thing about releasing Canary every day is that updates and bug fixes can be shipped quickly too. Occasionally, a Canary build may even have a bug that makes the browser crash or be completely unusable on some sites. We add changes and new features to the Canary channel with minimal testing. Chrome Canary helps us try out changes with real users and developers, to test for glitches before they become a problem. ![]() This is the most experimental Chrome channel, including new and experimental features. This channel is like the proverbial canary in the coalmine. Within each channel, Chrome deploys a series of versions which indicate the order of release and degree of change from previous versions. There are four varieties of Chrome available at any one time, on mobile and desktop platforms: Canary, Dev, Beta and Stable. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |