Derek Fountain tapped away at the keyboard with:
I think there should be, but they seem to do it all in house. After the mess that 6.4 was (shipped with a broken *Netscape* for crying out loud) they clearly need to do a better job. A public beta strikes me (and Redhat, and Debian, etc) as a very good idea.
Netscape wasn't known to be broken when 6.4 was put together. It ran out of the box. They also shipped a broken "nn"; which is a far greater crime from my point of view, especially as it wouldn't even run out of the box. Even if you interpose a public beta before release, bugs will still crawl through. A beta programme would also delay a release by several months, making SuSE "hopelessly out of date" in comparison with the lesser distros. Some/more regression testing is called for to identify the "no-starters". To that end, every package *should* include rules and/or tools for regression testing of that package. That would help to enforce the Unix-like process of combining stable components to build a system or distribution. It can also be used to "certify" systems that have been modified from the standard distibution. If that sounds too much like Engineering; then I apologize. -- Bernd Felsche - Innovative Reckoning Perth, Western Australia -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq