Quote
Originally posted by Slug:
**I agree with David, in-house beta is much quicker. When I was building Iron Fist, I considered releasing it to Beta, but I had to go to Arizona for about a month. I brought my laptop and programmed..... Nothing else to do in Arizona
Well, when I got back, Iron Fist was so fit I decided to skip beta and release it in full (followed by a newer version a few days later). I'm glad I didn't put it to Beta, I'd probably still be working on it....
Beta Testers suck. They only volunteer so they can get a copy of the plug early, not so they can help make a plugin. They never do any actual work except play it and complain loudly. However my next plugin, StarLance, a huge total converstion (still in concept, I have all the resources of Axis Software at my fingertips now....) will no doubt need a small army of testers....
O well, I'm rambling. Shut up, Slug.
**
Why do you think you seed it to as many as possible a open beta is sometimes far superior for the task cause you'll have those dedicated few who want to see it suceed and are happy when they see there suggestions implemented.
Its the long wait for updates that usually shoot beta testers off. I know in-house its edited, BOOM! Joe, try it out, wow, it works, ok, lets add this, BOOM! It works, ok Joe lets try this, CRASH! ok it's fix and BOOM! wow, it works...
Nice and quick like a Fascist government leader giving orders.
Seeding public betas and the like is like democracy, the people who care tell you what's wrong, and enjoy seeing their efforts rewarded, unfortunatly, it has to go through cabinent, supreme court if need be, etc than it needs to be implemented which takes resources, time effort, a new way of thinking sometimes. It takes a long time.
------------------
"Don't steal. The government hates competition."
Star Trek Escape Velocity
http://homepage.mac.com/startrekev/