>From doing beta testing, I've seen this before. A company releases a
beta, it gets tested and the bug reports are submitted. They then fix
the bugs and release the product without doing a final evaluation of
the product on their beta list. (hint, hint)
Just a reminder for you guys at mandrake. The average numbewr of errors
intrduced by bug fixes is one bug for every ten fixes, testing can
catch enough of them to reduce this to one in one hundred. You should
NEVER release a product that has had a large number of patches applied
without running it through a final round of testing. Here's an example
of why.
The 3D package I beta test for on Windows released a new version
(against the objections of the testing team) after fixing a huge list
of bug reports. The package was released to the general public (at
$1200 a copy) and the following functions had been broken
by the bug fixes:
Rendering- lens flares, opacity, animation rendering, and several
texture mapping features
Animation- Key framing was broken
Modeling- boolean functions- one of the major cool modeling features,
and one of the spline modeling tools.
Several other problems that would lock the program.
This gave them a black eye they still haven't recovered from. There's a
lesson to be learned here guys. I happen to really like what you
are doing with the Mandrake release and I'd hate to see the same thing
happen to you.
Sam
On Thu, 27 Jan 2000, you wrote:
> On Mon 28 Feb at 04:49:12 +0000 [EMAIL PROTECTED] done said:
> >
> > Same problem here on two different machines. Is this being worked on /
> > fixed ?
> > At present I have Mandrake 7 CDROM which is totally useless.
>
> I don't mean for this to sound accusatory, but I thought this would have
> been tested a bit more thoroughly before release. This seems to be a
> problem that unfortunately occurs more and more regularly regardless of
> distro.
>
> BTW: What was the reasoning for making the leap to 7.0 from 6.1?
