Chromium Blog
News and developments from the open source browser project
Google Chrome in a Coal Mine
Monday, August 2, 2010
Since Google Chrome launched almost 2 years ago, the team has embraced the “launch early and often” strategy by releasing Dev channel builds almost weekly. But sometimes, such as when we’re in the process of moving a Dev channel release to the Beta channel, we’re unable to release a new Dev channel build, and other times, even a week is too long to wait to get feedback from the field on a change.
The team considered updating the Dev channel more frequently, but doing so would require us to forgo our manual testing pass on these builds. Even though the Dev channel is often rough around the edges, we realized that this lack of testing would result in a Dev channel that’s too unstable even for early adopters and developers. That’s why, a few days ago, we released a new experimental version of Google Chrome called Google Chrome Canary Build. We plan to update the Canary Build more frequently than the Dev channel, with riskier changes, and usually without a human being ever verifying that it works, so the Canary Build is only for users who want to help test Google Chrome and are comfortable using a highly unstable browser that will often break entirely. To enable you to continue using the same browser you love when the canary croaks, we’ve made it possible to install the Canary Build in addition to the Dev, Beta or Stable channel versions of Google Chrome.
The Canary Build is still brand new so it currently has a few limitations. Currently, it’s only available for Windows and cannot be set as your default browser. You can star the issues for
Mac
and
Linux
support, as well as the
issue
for default browser support to cast your vote and be notified of progress there.
If you like to live on the bleeding edge, give the
Google Chrome Canary Build
a shot and let us know what you think. The early feedback on crashes, performance regressions, broken features and other problems is incredibly valuable to us, so thanks!
Posted by Henry Bridge, Product Manager
Labels
$200K
1
10th birthday
4
abusive ads
1
accessibility
1
ad blocking
1
android
1
benchmarks
1
beta
14
billing
1
birthday
4
blink
1
browser
2
browser interoperability
1
capabilities
3
capable web
1
cds18
2
cds2018
1
chrome
11
chrome ads
1
chrome apps
3
chrome dev summit 2018
1
Chrome Frame
1
chrome web store
27
chromedevtools
1
chromeframe
3
chromeos
3
chromium
3
cloud print
1
coalition
1
coalition for better ads
1
dart
8
dashboard
1
day 2
1
design
1
devtools
12
discoverability
1
extensions
24
features
1
feedback
2
field data
1
frameworks
1
fund
1
funding
1
gdd
1
googlechrome
12
harmful ads
1
html5
11
incognito
1
javascript
3
lab data
1
lighthouse
1
linux
2
mac
1
mobile
2
na
1
native client
8
New Features
5
octane
1
open web
3
pagespeedinsights
1
performance
2
performance tools
1
play store
1
portals
1
progressive web apps
1
protection
1
pwa
1
releases
3
rlz
1
security
30
spdy
2
speed
1
ssl
2
store listing
1
subscription pages
1
tools
1
trusted web activities
1
twa
1
v8
6
web apps
1
web intents
1
web packaging
1
web.dev
1
webapi
1
webaudio
3
webgl
7
webkit
5
webmaster
1
webp
5
webrtc
4
websockets
5
webtiming
1
writable-files
1
Archive
2019
Feb
Jan
2018
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2017
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2016
Dec
Nov
Oct
Sep
Aug
Jun
May
Apr
Mar
Feb
Jan
2015
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2014
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2013
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2012
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2011
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2010
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2009
Dec
Nov
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2008
Dec
Nov
Oct
Sep
Feed
Google
on
Follow @ChromiumDev
Give us feedback in our
Product Forums
.
