OMEN
01-09-2009, 11:58 PM
Revamps auto-update mechanism to offer 'stable,' 'beta' and 'dev' builds
Google Inc. yesterday announced that its Chrome browser would be in a "never-ending" beta test, and it gave users three options for updating their copies at varying intervals.
Although the search company stripped the beta label from Chrome a month ago, yesterday it said it was revamping how it updates the browser so that some users would essentially be participating in "a never-ending Beta test."
Rather than using just one "channel," the term it has used to describe the update mechanism for not-quite-ready versions of Chrome, Google has shifted to three, Mark Larson, a technical program manager with the company, said in a blog post Thursday.
"The channels are essentially a never-ending Beta test and a continuous feedback loop that lets us rapidly develop new ideas into solid product features," argued Larson.
The three channels include Stable, Beta and Developer Preview.
Stable means finished and polished, "rock solid," said Larson. It's the update channel set by default in Google.
Beta includes features that Google deems suitably reliable for wide testing, and it will be refreshed about once a month, according to Larson. "The Beta channel is more stable than Dev, but may lack the polish one expects from a finished product," he said.
The Developer Preview channel means, "very unstable at times," said Larson. It includes new features that will probably require some manual configuration in order to be enabled.
Users who want to subscribe to either the Beta or Developer Preview channels can do so by downloading and running a small utility, available here. Google Chrome Channel Changer 2.0 offers the three choices -- Stable, Beta and Dev -- that Larson spelled out.
Users who tried an earlier version of the channel-changing utility to get frequent developer builds have been automatically moved to the Beta channel, added Larson. The new Developer Preview channel is "less polished than what [previous] Dev channel users have been getting during Google Chrome's Beta," he explained.
Larson also used the opportunity to get in a not-so-subtle dig against browsers from rivals such as Mozilla Corp. and Microsoft Corp.
"We want to release fewer features more often instead of making you wait 12 months for the next Major Dot-Oh Release Jam-Packed With Features," Larson wrote. "Because we don't have those big Dot-Oh release milestones on the calendar, we don't have long periods of new features."
Both Mozilla, the maker of Firefox, and Microsoft, whose Internet Explorer still accounts for nearly 70% of all browsers, rely on periodic major updates that go through long periods of beta testing. Mozilla, for instance, is working through beta testing of Firefox 3.1, the successor to Firefox 3.0, which launched in June 2008.
Also yesterday, Google said it had updated the Developer Preview channel to a new build, tagged as "2.0.156.1," that includes a host of additions and improvements. They include a new auto-complete feature that fleshes out partially-typed entries in online forms, another that "docks" tabs dragged to the desktop's top, bottom and sides.
Chrome 2.0.156.1 also uses a newer version of WebKit -- the open-source browser engine that powers Chrome and Apple Inc.'s Safari -- as well as the newest version of Google's own V8 JavaScript engine.
According to data from Web metrics firm Net Applications Inc., Chrome had a 1% share of the browser market last month, a record for the browser.
[B]Compworld
Google Inc. yesterday announced that its Chrome browser would be in a "never-ending" beta test, and it gave users three options for updating their copies at varying intervals.
Although the search company stripped the beta label from Chrome a month ago, yesterday it said it was revamping how it updates the browser so that some users would essentially be participating in "a never-ending Beta test."
Rather than using just one "channel," the term it has used to describe the update mechanism for not-quite-ready versions of Chrome, Google has shifted to three, Mark Larson, a technical program manager with the company, said in a blog post Thursday.
"The channels are essentially a never-ending Beta test and a continuous feedback loop that lets us rapidly develop new ideas into solid product features," argued Larson.
The three channels include Stable, Beta and Developer Preview.
Stable means finished and polished, "rock solid," said Larson. It's the update channel set by default in Google.
Beta includes features that Google deems suitably reliable for wide testing, and it will be refreshed about once a month, according to Larson. "The Beta channel is more stable than Dev, but may lack the polish one expects from a finished product," he said.
The Developer Preview channel means, "very unstable at times," said Larson. It includes new features that will probably require some manual configuration in order to be enabled.
Users who want to subscribe to either the Beta or Developer Preview channels can do so by downloading and running a small utility, available here. Google Chrome Channel Changer 2.0 offers the three choices -- Stable, Beta and Dev -- that Larson spelled out.
Users who tried an earlier version of the channel-changing utility to get frequent developer builds have been automatically moved to the Beta channel, added Larson. The new Developer Preview channel is "less polished than what [previous] Dev channel users have been getting during Google Chrome's Beta," he explained.
Larson also used the opportunity to get in a not-so-subtle dig against browsers from rivals such as Mozilla Corp. and Microsoft Corp.
"We want to release fewer features more often instead of making you wait 12 months for the next Major Dot-Oh Release Jam-Packed With Features," Larson wrote. "Because we don't have those big Dot-Oh release milestones on the calendar, we don't have long periods of new features."
Both Mozilla, the maker of Firefox, and Microsoft, whose Internet Explorer still accounts for nearly 70% of all browsers, rely on periodic major updates that go through long periods of beta testing. Mozilla, for instance, is working through beta testing of Firefox 3.1, the successor to Firefox 3.0, which launched in June 2008.
Also yesterday, Google said it had updated the Developer Preview channel to a new build, tagged as "2.0.156.1," that includes a host of additions and improvements. They include a new auto-complete feature that fleshes out partially-typed entries in online forms, another that "docks" tabs dragged to the desktop's top, bottom and sides.
Chrome 2.0.156.1 also uses a newer version of WebKit -- the open-source browser engine that powers Chrome and Apple Inc.'s Safari -- as well as the newest version of Google's own V8 JavaScript engine.
According to data from Web metrics firm Net Applications Inc., Chrome had a 1% share of the browser market last month, a record for the browser.
[B]Compworld