On Thu, 23 Oct 2003, Steinar Hauge wrote: > No, you should continue to provide bug fixes and updates as well!! :-) > Thats one of the reasons why I am a club member. > > But what you should consider, is to use a little bit longer time and have a > RC3 cykle also. It is a pity that MDK has got a reputation(from people I talk > with) to be a little bit buggy distribution. An RC3 will give people like me, > that cant take the risk to put a beta version into production, the chance to > do some final testing on a release, that hopfully is stable enough for a > production environment. So why this suggestion? Because I do not have that > many PC for testing and I have to test it on my "production" laptop as well. > Did this with 9.2 RC2.
More RCs done help as long as the differences between RCs remain as big as they are now. Sometimes you see entire new (Mandrake-patched) versions of software, instead of known-stable versions. And sorry to say, but I'm not really happy with all this Mandrake-patching. Those LG cdrom drive-problems would rather probably not happen if Mandrake used an official kernel that is out a few weeks instead of shifting to Mandrake patchlevel X in the last RC, which is patched again and goes untested into the final. An other example: Mandrake supports software suspend, a feature that is known to be buggy and absolutely not mature in 2.4. It crashes my PC. You don't need a certain amount of RCs, you need RCs till nobody reports problems anymore that are serious enough to hold you back from renaming he latest RC into FINAL __without any modification__. Jos
