04-04-07, 05:15 PM
|
#26
|
Seasoned Skipper 
Join Date: Mar 2001
Location: cape cod mass.
Posts: 678
Downloads: 59
Uploads: 0
|
Quote:
|
Originally Posted by modisch
Quote:
|
Originally Posted by TheSatyr
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).
|
ah, you used the proper method. You need to revise this for UBI...
1)Devs play golf.
2)Loser of dev golf makes a patch build.
3)Intern checks that the patch build doesn't crash his computer immediately upon installing.
4)Devs play more golf. Interns caddy.
5)Loser of golf game sends patch to UBI for release.
6)Intern at UBI puts it on the intarwebs.
7)Gaming community beta tests, discovers newly added bugs, complains in forums
8)Return to step 1.
That's more like it.
-m |
lol
|
|
|