Quoting Buchan Milne <[EMAIL PROTECTED]>:
> of "If you want to ensure your hardware works, you *must* test beta1". > > Buchan Agree. I posted a similar message just after the final release. Maybe the more efficient way is to : - rename the beta to RC directly, or just use 1 beta. Psychologically, a lot of people try only the latest RC, thinking that bugs will be found by the other people... - fake that the final release date is actually 1 or 2 weeks before the real release date, since most of the bugs arrive at the last minute, so that it leaves more time to correct last minute bugs. - maintain a database of "official" beta testers, with their hardware specs. So that it would be interesting for two things : First it would give an idea of the most used hardware, so Mdk would concentrate on that hardware Second, it would allow to test some specific hardware : if there is a doubt about this or that hardware detection, Mandrake would just have to contact that (these testers) to ask to test their specific configuration. - maybe offer 10% discount on subscribing Mandrake club for the 50 people who have reported the most bugs (non redondant) ? Except that it would maybe attract not serious people who try to report bugs just for discount. But since registering on Bugzilla is necessary, this would limit this issue. WDYT ? Eric
