Unfortunately, for those of you who may not be aware, pushing updates is not as simple as copying a file to a server and pushing a button.
Once Google provides the updated code to the phone maker, they go through it with fine toothed comb, add in their specific add-ons (except Nexus) then test and test and test. When they feel it's ready, they push to each of their OEM's like Telus, Rogers and Bell. All of this is controlled by Country obligations (India got M first, no idea why but they did), regional OEM (AT&T, Telus, Orange etc) and by things like volume sales and so forth.
Once Telus gets their hands on it, they go through it with fine toothed comb, add in their specific add-ons (except Nexus) then test and test and test (again). If anything comes up, it's back to square one. Fix it, then then test and test and test. Now imagine that this has to happen for ALL the devices that are identified as recipients by the manufacturers (HTC, LG, Samsung, Kyocera, etc). Resources are not limitless (although that's a seperate arguement altogether).
Now that all the testing is done, the scheduling begins, again perhaps the contractual obligations come into play (or not) however each scheduled device has a deployment date (usually includes a claw back period in case something nasty comes out that wasn't found in testing. Rare but it happens). And each device goes through the process.
So, for all of you raising concerns about why a device date was missed by a day or two or telling a service provider to "get your freakin act together", realize that you are part of a much larger project and your specific device may or may not be high up on the global deployment plan. Nobody is going to die if the upgrade takes a day or a week or a month longer. Chill out and be surprised when it does arrive. Just like Xmas only better.
