No. 1 Story

HP job cuts loom for Australian employees

A number of Australian employees of Hewlett-Packard are facing the loss of their jobs as the global computer giant looks to slash its worldwide workforce by up to 30,000.

read more

Related Articles

Google, offers, delay, new, Google, Apps, features
Oracle has announced the latest version of its SaaS CRM solution, CRM On Demand...
IBM OmniFind Personal Email Search (IOPES) goes beyond simple word matching to incorporate concepts...
Significant features previously planned for the first version of Microsoft Windows Server virtualisation (code...
VoIP service provider, Freshtel, has unveiled its new VoIP network, dubbed V2 Voicedot, claimed...
Ericsson is to collaborate with Sun Microsystems to develop an open source Java technology-based...

Google offers to delay new Google Apps features

Business IT - Technology

It may seem strange to you, but not everyone wants the latest features of Google Apps as soon as they are available.


One of the big attractions of web applications (whether you call them SaaS, cloud or anything else) is that you don't have to mess around with updates. The provider implements a new feature, and it's there the next time you use the application.

But some administrators want time to check out the changes, perhaps in order to determine whether any compatibility issues arise, to determine whether any new procedures are needed, or to notify users of the change and possibly deliver any training that's thought necessary.

To accommodate such customers, Google Apps is moving to a two-track scheme for introducing new features.

Most users will remain on the 'rapid release' track and continue to see new features and other changes as soon as they are deployed. But administrators can choose to put their users on the 'scheduled release' track instead.

Accounts set for scheduled releases will get new features on Tuesdays (presumably US time), giving administrators a minimum of seven days to check out the changes.

So how do you find out what's coming? See page 2.