really? how about you go back through this thread and read why not.
edit: you where asking for specific dates, they already give timelines which is not specific dates. they say things like this summer, winter, fall, etc.
Printable View
Like this one you mean.
http://www.youtube.com/watch?v=C1Ww9...ailpage#t=157s
When you implement content that needs to be tested extensively in-house, not only you don't know *for sure* when that content will be finished until you're quite near to finishing it (since the synergie between different teams are complex, and often if something goes wrong within a team, it delays the work of other teams as well, in a cascade reaction), but you also have to take in account the very concrete possibility that the finished content will go to the QA team for internal testing, some critical bug, problem or incompatibility is found, and the whole piece of content/system needs to go back to development in order to be fixed. Then it needs to go back to QA in order to be tested again (and they cannot *just* test the fix, but they need to test much more extensively to make sure that the fix itself didn't cause other bugs or incompatibilities) and so forth.
The problem with announcing timeframes early in this conditions is that most gamers do NOT know or aknowledge the above problems, and take a missed timeframe as a broken promise, resorting to venting their frustration by flaming the developer or even quitting.
That's why not announcing timeframe until such timeframes are set in stone is a golden rule, and you won't see SE breaking it. Yoshida himself said, in one of his first interviews, that he's simply not going to make promises until he is sure that he can keep them.
Hello Everyone,
As two of our Community Reps have already provided answers to the questions and due to the off topic posts, we are going to go ahead and close this thread.
Thank you for your understanding.
-Senior Game Master Jhanaka