There are alot of people who have no clue as to what it would take for HT to maintain and balance 2 code bases (AH I and AH II are 2 different animals) ... nor do they realize the $ cost of maintaining multiple (duplicate) servers to run both AH I and AH II at the same time.
If AH I were kept alive, which version gets the attention of HT. I can see the mayhem when HTC annouces new plane additions to AH II and the AH I crying for the same planes ... again ... remember that planes in AH II cannot function in AH I, so HT would have to duplicate the effort for AH I.
Key word in all of this is DUPLICATE. Duplication in the software world is STUPID and guaranteed to cause more problems than its worth and results in loss of money. I don't know about you, but I don't think that HTC goal is to lose money at the rate that "duplication" would create.
Then when it's truly ready do a weekend {mainly because #'s are up then} test with the AH community, get the feedback, see what's up.
Then when Monday rolls around HTC can say A}we need to work out this or that
B}We nailed it, AHII now open for business
You're kidding Moil .. right ?
We did the Beta thing ... a lot of us ... and from that statement, it appears that you didn't.
The logic in your statement is exactly what the Beta accomplished as far as HTC was concerned, so feel comfort in the fact that this was covered by a whole lot of Beta testers over the last month or so.
There is a magic point in software development/deployment where you just have to throw the switch and at that point you don't look back. I am a software developer by profession, and IMO HTC was not premature in their decision to go live with AH II.