That's why you use a sampling of data when beta testing. This type of glitch is not related to load testing. I frequently help beta test our software at work. It's not unusual for it to take almost a year for the public version to be distributed. Even when select clients are helping to beta test it toward the end, they realize the data they are using is not live production stuff. I don't believe most of the problems so far here with the boards have been related to the data volume aspect, more to do with functionality. This was probably rushed to the public a little too hastily. And ancestry.com should have asked CC volunteers to test it before it was released. Most of us would have been willing to do so in order to avoid the situation we are currently experiencing. My 7.5 cents... Joe D. Deaver TXBELL Coordinator http://www.rootsweb.com/~txbell ancestry@deaver.com -----Original Message----- From: W. David Samuelsen [mailto:dsam@sampubco.com] Sent: Tuesday, June 26, 2001 2:07 PM To: RootsWeb-Help-L@rootsweb.com Subject: Re: [RW-Help] New Messages no Longer sent to list the glitch is that if they test through the merger while still have the old ones open, the new messages will be lost when testing is over. Hence the glitch. David

Joe Deaver wrote: <<I don't believe most of the problems so far here with the boards have been related to the data volume aspect, more to do with functionality. >> Yes! The major problems I'm seeing are not minor bugs. They evolve around the more serious functionality problems. A major system of this sort should never have gone live until the basic functions had been seriously beta tested. It is obvious, from what I've seen, that this system was "rushed" into production. And from what I'm seeing, fixes are being reported to staff that have NOT been fixed, and the bugs seem to be multiplying like rabbits. Fix one, add two more :-) Nel