Skip to Content
9-18-2007 @ 6:17PM
I think it's quite likely that 2.2 has been blocked by tech issues for weeks, and the content team has been hard at work on 2.3 for all that time (in fact, I wouldn't be surprised if they've wrapped 2.3 and are working on 2.4)In any development effort the size of Blizzard's, all the work is pipelined. I _guarantee_ that there have been stressed-out meetings where the content guy pounds his fist on the table and says, "Dammit, we need to get the 2.2 content out there, can't you guys slip the voice work into 2.3?" and the QA guy says, "No way. Rolling back the changes, merging the new code into the 2.3 branch, and restarting the QA process would take much longer." And then the product manager puts her head in her hands, breathes deeply five times, and says, "Ok, dev, get your guys back to work on those sound bugs. We'll find some bonus money for 'em, try to get them to work this weekend.".That's how software gets made. :)
First time? A confirmation email will be sent to you after submitting.
Members enter your username and password.
Enter your AOL or AIM screenname and password.
Please keep your comments relevant to this blog entry. Email addresses are never displayed, but they are required to confirm your comments.
When you enter your name and email address, you'll be sent a link to confirm your comment, and a password. To leave another comment, just use that password.
To create a live link, simply type the URL (including http://) or email address and we will make it a live link for you. You can put up to 3 URLs in your comments. Line breaks and paragraphs are automatically converted — no need to use <p> or <br /> tags.