1  |   Order by index

Sep 24, 2002, 5:34pm

I think the beta should test one feature at a time. They should test just
that one feature and after a week or two of very little or no bugs found, it
should be released to the public. That way there are updates more often to
interest the public and testing will be better because each feature will get
lots of attention from the beta-testers.

-Dion

Nov 25, 2002, 1:24am

That's a bit like trying to write a novel by asking your proof readers to examine it after each addition, deletion, or change of single sentance or paragraph, and publishing a new edition of the book for the public to upgrade to every time another section of a chapter is completed. There are problems with this type of aproach. Yes, the book would be pretty much error free at each new release, and yes people would be able to get a new edition more frequently, but writing a reasonable sized book that way would take a very long time, and if the author decided half way through writing the third chapter that they needed a character and situation added to the first chapter to support part of what they are planning for the fourth chapter, the process of editing chapter one, having it proof read, and publishing a revised edition would hold up work on chapter three and leave people wondering why the book was released with chapter three looking like someone forgot to finish it.

When AW 3.4 comes out... try carefully counting the number of things in it that could have been released one at a time, including the modifications along the way and things that were tried and then decided against, and run a little calculation to see how many years that would have taken. I think you'll be glad they didn't do it that way.

TechnoZeus

[View Quote]

1  |   Order by index