The Steps needed for a patch to be released:
1)Devs create a patch build
2)Beta testers test patch build...crunch some bugs
3)Devs create a new patch build
4)Beta testers test new build...crunch more bugs
5)Rinse and repeat steps 1-4 till Devs and Beta testers are satisfied
6)Devs send patch candidate to Publishers QA
7)Publisher QA passes the patch and patch is released and sent to download sites or:
8)QA finds problems and sends patch back to Devs where steps 1-6 are repeated until Publishers QA is satisfied. Then patch gets released and sent to download sites.
Which is why you get "when it's done" as an answer. It's not the Devs call on when to release a patch. It is almost always up to the Publisher. (Unless the Devs ARE the Publishers).
Finally,the more bugs that are on the "to fix" list,and the more features that might be added means longer testing times. And if (which is a real big IF) they also intend on adding more video cards to the "supported list" than that will take even more testing time. (Though that might get it's own specific patch down the road).
I doubt even the devs could give you an honest answer on when the patch will be done. There are just too many variables involved.
(Now watch them prove me wrong and have the sucker out next week...*lol*).
|