The broader point is valid, though. Google needs to make this happen, no one in the rest of the bucket brigade (not the handset vendors, and certainly not the carriers who bear the costs) cares about updates -- only Google and the users do. Or at the very least make it clear why, when AOSP "releases" a version, certain developer phones won't be getting it.
I think Google are going to be addressing this in a big way in the US with their recent move to sell unlocked devices directly to consumers. [0]
I am quite interested to see how CDMA (Verizon, Sprint) factors in to Google's latest device play (since CDMA devices, even "unlocked" ones, need to be approved by the carrier to be activated).
0: http://online.wsj.com/article/SB1000142405270230437150457740...
Apple's answer, of course, is "... or else you won't get the next iPhone."