Pixel wrote: > > Ron Stodden <[EMAIL PROTECTED]> writes: > > > Mandrake 8.2 is plainly > > still in Alpha test and they are improperly co-opting us outside users > > to assist that process, which should be an internal function. I am > > looking forward to when Alpha has been completed and Beta and then Gamma > > testing can commence, but regretfully (and foolishly) that has not > > happened for any Mandrake release so far. > > It won't happen. If you want this kind of slow release, go to Debian. No > offense to Debian of course, our time to release/market are quite different > (FYI, I have a chroot 'unstable' debian on my box)
Then start your whole release cycle 2 (or 6?) months earlier and make a point of ensuring all reported bugs are corrected. This should eliminate the great rush at the end and mistakes made by tired people. It would also make an enormous difference if you Mandrake people actually started USING the software you deliver and ran networked development and QA areas so that the networking problems would show up. Simple example: There is a bad bug in nfs that I have just verified is still present between two 8.2 network nodes. The binary exportfs list gets screwed up quite frequently. When in this state access to only 1 or 0 files is made available to the requester without any warning or error messages whatsoever, and with the result that whole partitions can be quietly lost when rsyncing. If you happen to notice it, the fix is very simple, just rerun exportfs -r on the machine that has the source files and redo the rsync. But this not trivial bug has been with us since at least 7.2! -- Ron. [au]
