Verno wrote on Jun 22, 2011, 10:17: Chrome has been doing that for ages. It's not for no reason, it's to increase the pace of release because they were consistently late hitting milestone releases.
So, it's not for "no" reason. It's for a bad reason. How does calling a release 5 instead of 4.1 slow you down if your working on exactly the same features and fixes? You've lost the information gained in the major/minor versioning scheme, and gained nothing in return.