![]() ![]() Future updates in 2017 should appear the weeks of Sept. "These dates are subject to change without advance notice and provided here only for rough planning purposes," Google's Chromium team states there.Ĭhrome 59 should update to Chrome 60 shortly, during the week of July 23-29. Unofficially, users can view Chrome's estimated release schedule here, to get an idea of when the next version will be distributed. Officially, Google recommends that users frequent this blog to track just-issued updates, including the security-only fixes that pop up at irregular intervals between each polished edition's arrival. The company does not keep to a set schedule - as does, for example, Mozilla with its Firefox - nor does Google do much to trumpet each release. ![]() Google issues a new version of Chrome approximately every six weeks, although so far this year the average time between releases has been 47 days, or closer to seven weeks. How to know when Google will next update Chrome ![]() The ensuing page either reports "Google Chrome is up to date" or displays the updating process before presenting a "Relaunch" button. To manually trigger an update - to get the security fixes pronto when news of active attacks circulate, say - users simply select "About Google Chrome" from the Help menu under the vertical ellipsis at the upper right. Instead, the company spreads out the distribution over days, or sometimes even weeks. When Chrome does detect an available update, it downloads the new code and preps it for installation, although that latter step doesn't begin until the user starts or restarts the browser.īut not every copy of Chrome receives an update as soon as Google issues one. The browser periodically checks for updates Google's own documentation, which is often left long out of date on the firm's site, says in one place it does so every 23 hours and 20 minutes. Automatic updates, or manual triggerīecause Chrome does updates automatically, most users need do nothing but relaunch the browser once in a while to stay current. While this build does get tested, it is still subject to bugs, as we want people to see what's new as soon as possible.We've dug into Chrome's updates, from their frequency and schedule to how to manage them as an individual or as an IT professional. There's no lag between major versions, whatever code we've got, you will get. The Dev channel gets updated once or twice weekly, and it shows what we're working on right now. It's updated every week roughly, with major updates coming every six weeks, more than a month before the Stable channel will get them.ĭev Channel: Want to see what's happening quickly, then you want the Dev channel. It's updated roughly every two-three weeks for minor releases, and every 6 weeks for major releases.īeta Channel: If you are interested in seeing what's next, with minimal risk, Beta channel is the place to be. Stable Channel: This channel has gotten the full testing and blessing of the Chrome test team, and is the best bet to avoid crashes and other issues. ![]() For Ubuntu Linux as of the date of writing these are: In an attempt to make this out-of date question useful, Currently Chrome supports a number of different release channels. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |