google-chrome-logo

Google is not satisfied with the speed at with it’s browser Chrome is being updated now… so it is further increasing the speed of at with Chrome would be updated. Google is going to release a stable version of chrome every six week. With this the version numbers and features that every version would get insignificant.

Google has given various reasons for this update –

      • Shorten the release cycle and still get great features in front of users when they are ready
            • Make the schedule more predictable and easier to scope
          • Reduce the pressure on engineering to “make” a release

Under the old model, when we faced a deadline with an incomplete feature, we had three options, all undesirable: (1) Engineers had to rush or work overtime to complete the feature by the deadline, (2) We delayed the release to complete that feature (which affected other un-related features), or (3) The feature was disabled and had to wait approximately 3 months for the next release. With the new schedule, if a given feature is not complete, it will simply ride on the the next release train when it’s ready. Since those trains come quickly and regularly (every six weeks), there is less stress.

So is this a good think or not?? I don’t think so… Google could always release minor updates as necessary like Firefox does – 3.0.1 to 3.0.2 — instead of jumping from version 4 to 5 to 6 without any major changes or added features.

This is entirely different from what other browsers or software do… Google has asked not to read too much into the pace of version number changes…. people do care about version numbers.

Somewhere around next year you would most probably be using Google Chrome version 20 or version 25 ;D