I think we have to analyze why many people don't have keen interest to testing
real tesing have to be done on a day to day use (apart from install stuff). So, IMHO, the tesing should divided in steps: * first step: install. use the basic dvd and network, etc... only with the basic config. If it installs: pass, if it don't->bugzilla. We are just now on this side with 10.2 * make a live cd with just this basic software and possibly all the hardware modules available. Testing all network and wlan is extremely important * make a general call on opensuse list: try to install the basis, try the live cd and report pass/don't pass with the hardware info (very important) - this is fast and easy, so many people is able to do * try to install and use most usually used aps. For me it's Mozilla and Thunderbird, then digikam. With this, I begin to be able to work with the new install. then go on with more apps, of course. Once a module or an app is validated by a sufficient number of users, slowdown any new feature on it. you can without doubt (you, any reader here) add some important apps jdd -- http://www.dodin.net http://valerie.dodin.org http://www.youtube.com/watch?v=t-eic8MSSfM http://www.facebook.com/profile.php?id=1412160445 -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-testing+help@opensuse.org