Without wanting to be a troll, the blog entry merely points out factors that are standard operating procedure for the majority of product-driven embedded work. Google cannot realistically share details of their release schedule - which would divulge market-influencing product release schedules.
Also, customization is still such a large part of building an embedded product, that following, rather than leading, other open source developers working on the same project is really not an option. Time-to-market pressures are had everywhere - so I'm not using that as an excuse. But product-specific features, unlikely to be mainline-able in the short term, are required to get the product out the door.
Would the author have been happier if Google had pushed all code upstream first, before releasing their product. We'd still be waiting for the first phone if they had done that. (And in many cases, just where would "upstream" be?)