You can now install/run two Google Chrome builds side by side:
- Install one of Google Chrome stable/beta/dev releases as usual. - Install Google Chrome canary build (Windows only for now) which will be installed to different path, get updated separately, and run side by side with existing stable/beta/dev installation.
In usual situation, the canary build will be same as dev build. Sometimes if necessary, we may push additional update on canary build so its version is higher than dev. This may happen in following possible scenarios:
- When a beta branch is cut and a dev build is released from the beta branch, we may release a canary build from trunk so we have user coverage for builds from trunk. - When we need to release a risky dev build, we may push it to canary build first for test.
*If you are doing development/test for chromium project or interesting in getting involved, we recommend you install Google Chrome canary build and use it on daily basis.* It helps you keep track of activities from both trunk and release branches. You can get Google Chrome canary build from:
You can click the above download link and start installation without exiting your current running Chrome, regardless which channel it is on. Once done, the installer will install Google Chrome canary build to a separate directory with different default user profile, short cuts, and icons, i.e. everything should be separate from existing Google Chrome installation.
I've been running Canary and Beta side by side on Windows (note: Canary is Windows only right now), and I've found it very useful.
The canary usually updates more frequently than the Dev channel (higher risk of bustage), and we're working on making it update as often as we have successful nightly builds. When something doesn't work on the canary, I can just fall back to my Beta Google Chrome.
I recommend it for anyone who wants to help test the latest Chrome features. The data we get back from canary users --especially crash statistics-- helps us find and fix regressions faster.
On Wed, Jul 21, 2010 at 22:57, Huan Ren <hu...@google.com> wrote: > You can now install/run two Google Chrome builds side by side:
> - Install one of Google Chrome stable/beta/dev releases as usual. > - Install Google Chrome canary build (Windows only for now) which will be > installed to different path, get updated separately, and run side by side > with existing stable/beta/dev installation.
> In usual situation, the canary build will be same as dev build. Sometimes > if necessary, we may push additional update on canary build so its version > is higher than dev. This may happen in following possible scenarios:
> - When a beta branch is cut and a dev build is released from the beta > branch, we may release a canary build from trunk so we have user coverage > for builds from trunk. > - When we need to release a risky dev build, we may push it to canary build > first for test.
> *If you are doing development/test for chromium project or interesting in > getting involved, we recommend you install Google Chrome canary build and > use it on daily basis.* It helps you keep track of activities from both > trunk and release branches. You can get Google Chrome canary build from:
> You can click the above download link and start installation without > exiting your current running Chrome, regardless which channel it is on. Once > done, the installer will install Google Chrome canary build to a separate > directory with different default user profile, short cuts, and icons, i.e. > everything should be separate from existing Google Chrome installation.
On Wed, Jul 21, 2010 at 10:57 PM, Huan Ren <hu...@google.com> wrote: > You can now install/run two Google Chrome builds side by side:
> - Install one of Google Chrome stable/beta/dev releases as usual. > - Install Google Chrome canary build (Windows only for now) which will be > installed to different path, get updated separately, and run side by side > with existing stable/beta/dev installation.
> In usual situation, the canary build will be same as dev build. Sometimes > if necessary, we may push additional update on canary build so its version > is higher than dev. This may happen in following possible scenarios:
> - When a beta branch is cut and a dev build is released from the beta > branch, we may release a canary build from trunk so we have user coverage > for builds from trunk. > - When we need to release a risky dev build, we may push it to canary build > first for test.
> *If you are doing development/test for chromium project or interesting in > getting involved, we recommend you install Google Chrome canary build and > use it on daily basis.* It helps you keep track of activities from both > trunk and release branches. You can get Google Chrome canary build from:
> You can click the above download link and start installation without > exiting your current running Chrome, regardless which channel it is on. Once > done, the installer will install Google Chrome canary build to a separate > directory with different default user profile, short cuts, and icons, i.e. > everything should be separate from existing Google Chrome installation.
I have the Canary build installed. I am looking forward to help
continue testing Chrome. I've been testing with the Dev channel. Is
there a list of updates/fixes that are included in the daily builds?
ie: http://googlechromereleases.blogspot.com/ for the dev, beta and
stable channels. Thanks.
On Mon, Jul 26, 2010 at 8:06 AM, Cakalaky <jeremyebelc...@gmail.com> wrote: > I have the Canary build installed. I am looking forward to help > continue testing Chrome. I've been testing with the Dev channel. Is > there a list of updates/fixes that are included in the daily builds?
No.
The Mozillazine folks maintained a forum for the Fx nightlies that would have a new thread for each nightly, listing the changes, fixed issues, outstanding bugs, etc. This was all done by community members. It'd be great to have something similar for Chrome, if there are people out there who are passionate about this. You don't even need commit access to help.
> The Mozillazine folks maintained a forum for the Fx nightlies that would
> have a new thread for each nightly, listing the changes, fixed issues,
> outstanding bugs, etc. This was all done by community members. It'd be
> great to have something similar for Chrome, if there are people out there
> who are passionate about this. You don't even need commit access to help.
I'd be interested in participating in something like this
On Mon, Jul 26, 2010 at 11:22 AM, John Munro <ghost...@gmail.com> wrote: > > The Mozillazine folks maintained a forum for the Fx nightlies that would > > have a new thread for each nightly, listing the changes, fixed issues, > > outstanding bugs, etc. This was all done by community members. It'd be > > great to have something similar for Chrome, if there are people out there > > who are passionate about this. You don't even need commit access to > help.
> I'd be interested in participating in something like this
The Google employees working on Chrome are unlikely to take the lead in organizing this, so I encourage you (and anyone else interested) to just go ahead and make it happen.
On Thu, Jul 22, 2010 at 12:03 AM, Darin Fisher <da...@chromium.org> wrote: > Most excellent!!!
> One question: Why can't I make this be my default browser?
> Setting as default browser has not been implemented. (Issue 50117) > -Darin
> On Wed, Jul 21, 2010 at 10:57 PM, Huan Ren <hu...@google.com> wrote:
>> You can now install/run two Google Chrome builds side by side:
>> - Install one of Google Chrome stable/beta/dev releases as usual. >> - Install Google Chrome canary build (Windows only for now) which will be >> installed to different path, get updated separately, and run side by side >> with existing stable/beta/dev installation.
>> In usual situation, the canary build will be same as dev build. Sometimes >> if necessary, we may push additional update on canary build so its version >> is higher than dev. This may happen in following possible scenarios:
>> - When a beta branch is cut and a dev build is released from the beta >> branch, we may release a canary build from trunk so we have user coverage >> for builds from trunk. >> - When we need to release a risky dev build, we may push it to canary >> build first for test.
>> *If you are doing development/test for chromium project or interesting in >> getting involved, we recommend you install Google Chrome canary build and >> use it on daily basis.* It helps you keep track of activities from both >> trunk and release branches. You can get Google Chrome canary build from:
>> You can click the above download link and start installation without >> exiting your current running Chrome, regardless which channel it is on. Once >> done, the installer will install Google Chrome canary build to a separate >> directory with different default user profile, short cuts, and icons, i.e. >> everything should be separate from existing Google Chrome installation.
On Thu, Jul 22, 2010 at 12:03 AM, Darin Fisher <da...@chromium.org> wrote: > Most excellent!!!
> One question: Why can't I make this be my default browser?
> Setting as default browser has not been implemented. (Issue 50117) > -Darin
> On Wed, Jul 21, 2010 at 10:57 PM, Huan Ren <hu...@google.com> wrote:
>> You can now install/run two Google Chrome builds side by side:
>> - Install one of Google Chrome stable/beta/dev releases as usual. >> - Install Google Chrome canary build (Windows only for now) which will be >> installed to different path, get updated separately, and run side by side >> with existing stable/beta/dev installation.
>> In usual situation, the canary build will be same as dev build. Sometimes >> if necessary, we may push additional update on canary build so its version >> is higher than dev. This may happen in following possible scenarios:
>> - When a beta branch is cut and a dev build is released from the beta >> branch, we may release a canary build from trunk so we have user coverage >> for builds from trunk. >> - When we need to release a risky dev build, we may push it to canary >> build first for test.
>> *If you are doing development/test for chromium project or interesting in >> getting involved, we recommend you install Google Chrome canary build and >> use it on daily basis.* It helps you keep track of activities from both >> trunk and release branches. You can get Google Chrome canary build from:
>> You can click the above download link and start installation without >> exiting your current running Chrome, regardless which channel it is on. Once >> done, the installer will install Google Chrome canary build to a separate >> directory with different default user profile, short cuts, and icons, i.e. >> everything should be separate from existing Google Chrome installation.
So just to give me some basic direction - in order to do something
like the Mozillazine forum for the Fx nightlies, for each Canary
version I would get a list of the issues resolved? Or the revisions
in that version? Where would I get that from?
On Jul 26, 2:46 pm, Peter Kasting <pkast...@google.com> wrote:
> On Mon, Jul 26, 2010 at 11:22 AM, John Munro <ghost...@gmail.com> wrote:
> > > The Mozillazine folks maintained a forum for the Fx nightlies that would
> > > have a new thread for each nightly, listing the changes, fixed issues,
> > > outstanding bugs, etc. This was all done by community members. It'd be
> > > great to have something similar for Chrome, if there are people out there
> > > who are passionate about this. You don't even need commit access to
> > help.
> > I'd be interested in participating in something like this
> The Google employees working on Chrome are unlikely to take the lead in
> organizing this, so I encourage you (and anyone else interested) to just go
> ahead and make it happen.
On Wed, Jul 28, 2010 at 7:06 AM, John Munro <ghost...@gmail.com> wrote: > So just to give me some basic direction - in order to do something > like the Mozillazine forum for the Fx nightlies, for each Canary > version I would get a list of the issues resolved? Or the revisions > in that version? Where would I get that from?
The svn log. "svn log" in the root of a checkout will spit out the entire commit history for the repository in reverse chronological order. You can use -l <limit> to print only a certain number of entries.
On Wed, Jul 28, 2010 at 11:32 AM, Peter Kasting <pkast...@google.com> wrote: > On Wed, Jul 28, 2010 at 7:06 AM, John Munro <ghost...@gmail.com> wrote:
>> So just to give me some basic direction - in order to do something >> like the Mozillazine forum for the Fx nightlies, for each Canary >> version I would get a list of the issues resolved? Or the revisions >> in that version? Where would I get that from?
> The svn log. "svn log" in the root of a checkout will spit out the entire > commit history for the repository in reverse chronological order. You can > use -l <limit> to print only a certain number of entries.
Do we have the release log for canary builds? Or we are to check the
Chromium release logs for the corresponding version?
Also, please enable the option to make canary the default browser. I
wouldn't mind taking the risk of using a potentially unstable browser
for online shopping :).
On Jul 29, 12:08 am, Anthony LaForge <lafo...@google.com> wrote:
> Anthony Laforge
> Technical Program Manager
> Mountain View, CA
> On Wed, Jul 28, 2010 at 11:32 AM, Peter Kasting <pkast...@google.com> wrote:
> > On Wed, Jul 28, 2010 at 7:06 AM, John Munro <ghost...@gmail.com> wrote:
> >> So just to give me some basic direction - in order to do something
> >> like the Mozillazine forum for the Fx nightlies, for each Canary
> >> version I would get a list of the issues resolved? Or the revisions
> >> in that version? Where would I get that from?
> > The svn log. "svn log" in the root of a checkout will spit out the entire
> > commit history for the repository in reverse chronological order. You can
> > use -l <limit> to print only a certain number of entries.
It seems that for some reason the optional features like --enable-apps
or --enable-webgl are not working with the canary build, is there a
reason for that or am I doing something wrong?
Added a new /cl tool to omahaproxy, it gives you a delta between the current and previous release for a given os/channel pair (looking up the version, revision, and then redirecting to our CL tool). As one might expect, the url takes two parameters, os and channel.
Appropriate values for os = {win,mac,linux,cf,cros} Appropriate values for channel = {dev,beta,stable,canary}
> Anthony Laforge > Technical Program Manager > Mountain View, CA
> On Wed, Jul 28, 2010 at 11:32 AM, Peter Kasting <pkast...@google.com>wrote:
>> On Wed, Jul 28, 2010 at 7:06 AM, John Munro <ghost...@gmail.com> wrote:
>>> So just to give me some basic direction - in order to do something >>> like the Mozillazine forum for the Fx nightlies, for each Canary >>> version I would get a list of the issues resolved? Or the revisions >>> in that version? Where would I get that from?
>> The svn log. "svn log" in the root of a checkout will spit out the entire >> commit history for the repository in reverse chronological order. You can >> use -l <limit> to print only a certain number of entries.
> Added a new /cl tool to omahaproxy, it gives you a delta between the current
> and previous release for a given os/channel pair (looking up the version,
> revision, and then redirecting to our CL tool). As one might expect, the
> url takes two parameters, os and channel.
> Appropriate values for os = {win,mac,linux,cf,cros}
> Appropriate values for channel = {dev,beta,stable,canary}
> Anthony Laforge
> Technical Program Manager
> Mountain View, CA
> On Wed, Jul 28, 2010 at 12:08 PM, Anthony LaForge <lafo...@google.com>wrote:
> > I'll add something to omahaproxy shortly.
> > Kind Regards,
> > Anthony Laforge
> > Technical Program Manager
> > Mountain View, CA
> > On Wed, Jul 28, 2010 at 11:32 AM, Peter Kasting <pkast...@google.com>wrote:
> >> On Wed, Jul 28, 2010 at 7:06 AM, John Munro <ghost...@gmail.com> wrote:
> >>> So just to give me some basic direction - in order to do something
> >>> like the Mozillazine forum for the Fx nightlies, for each Canary
> >>> version I would get a list of the issues resolved? Or the revisions
> >>> in that version? Where would I get that from?
> >> The svn log. "svn log" in the root of a checkout will spit out the entire
> >> commit history for the repository in reverse chronological order. You can
> >> use -l <limit> to print only a certain number of entries.
