Added one for me!
Heh. But on a quasi-serious note, if you followed that addition strictly, you'd never get any software done. All version 1.0 software stinks. (I guarantee if you look hard at the exceptions, you'll find that they aren't really 1.0. This is why software that can't stink on launch has Alpha and Beta testing.)
See
Things You Should Never Do, Part I - Joel on Software for a good example of what can happen when you make a radical change to an existing product, too. (Gee, wonder why this applies?)
I've never had much faith in the upper management of WotC when it comes to software development. But if someone in middle management is doing the right thing (fixing crashes before features), the last thing we want is upper management jostling their elbows.
Really, the only things constructive that upper management could do on this right this minute is either offer alternatives or offer compensation. Give money back to subscribers. Throw money at the problem by running the old CB in parallel, using a different team (assuming that it is documented well enough to do that), until such time as the new version is ready to go. Offer reduced prices for the subscription in the interim. That is an upper management call. But someone decided to gamble that they could make the leap from old to new without a parachute, and now they are finding out what happens when the gamble fails.
If it were me, and I cared enough to make those previous kinds of gambles, then I'd shoot for the mid-term payoff. I'd run the online version as an open and free beta for three to four months (existing subscriptions being extended by the same amount). Get some good will, get a host of people hitting it, and get them hooked.