Looks like it's time to update the 'current documentation' - Let's also understand, we are all as anxious and excited for the new technology to be implemented as those writing it. I think we all waited for the ...next several weeks.... which have come and gone, and doubled, and added a week. I work in a large data center environment, I understand the why's etc, believe me....
But it is important to keep wards and stakes updated (These are your clients, we are your clients) this is called being service-oriented which I know the church departments are striving towards. Let me give you an example....based on the then known information, I made a case to our stake Presidency that we should hold off on converting to the new calendar stake-wide, because I understood a major version change was coming in June (knowing it could slip a bit - no worries there for me). I didn't want to go through the training, just to do it again in case things were that much different. I'm at a position again (I get asked questions EVERY week about it) of needing to know if I should do the training and get everyone migrated, or wait. This directly effects the callings and work of a large number of people in each of our stakes, we are all waiting on pins and needles, because, yes, we are excited about it... we're not nagging, we're eager. at least that's how I see it.
Additionally, let's not forget... Stakes are planning for next year, wanting to put a calendar together for 2012 by the end of September.... so that Wards and Branches can do their planning in Oct/Nov... The technology is a major part of that planning - just a quick updated is all we really need.
I don't think there is anything wrong with wondering if/when it is going to happen, or to request a better timeline about the release schedule.
“A long habit of not thinking a thing wrong, gives it a superficial appearance of being right, and raises at first a formidable outcry in defense of custom.”
― Thomas Paine, Common Sense