sigh
If you work in software development, you know there are ALWAYS software bugs present. Yeah, the 'development guidelines' want 100% coverage of testing cases, but as software complexity grows, the 100% mark grows what feels like exponentially -- generally no-one can afford to test all the possible permutations. It all depends on the risk associated with an error. For a game like CM, the bar can be much lower than, say, flight control software for a commercial airplane. Pixeltruppen meeting an untimely demise is vastly different than real world results.
Some errors you know about prior to release, some you don't until it is released "into the wild". People do unexpected things. I've been releasing software in one capacity or another since 1986, and nothing is ever perfect. You always strive to eliminate anything known to cause issues for X percent of cases. The question is always, "What is X? And where does a particular issue get prioritized? Above or below the line?"
IMHO, BFC does a good job of eliminating egregious issues and issues enjoyable, playable software. Patches follow to improve what has been released. I say go for it. I'd rather be playing than waiting forever...
And in the time honored legacy of all BFC releases: "What, you couldn't read the whole freaking email and keep quiet for the benefit of other pre-order folks? What a bonehead."
Pffft! Pay no attention to the back seat / woulda / shoulda / coulda commentary. You make your bets and you take your chances. It's all educational.
Thank you for providing ALL the AARs you have done over time (not just this one). For this one, had you hung back and not pushed hard early as you did, we would have missed out on the story thus far, or at least experienced a different story.
Perhaps the next one will be a more balanced meeting engagement...