rmatov101@charter.net said:
Well, here is what I see.
Problems in development release that scare 99% of todays users:
- boot configuration setup is black box, there is no list of
supported (to that moment tested) boot configurations. Actually there is no public specification what should go in this list: partitions, file system, permanent storage, (anything else)
probably first thing to do now
- kernel will not boot on certain hardware, how to debug this.
Reporting this requires a lot of text to be copied, once you make to
the usable configuration. Some simple numeric indicator like line number, or breakpoint number will help much more. It is easy to note on the paper, and easy to post. Splash screen during first phase of development that can have kernel crashes, should be forbidden.
* better, we should have test cd's with only the basic stuff (no install), but a debugging output, with copy to a disk if possible or to the screen if not.
* creating special, test time cd's should be the next goal
- X crashes, and nothing tells that Failsafe option offers a GUI
(it should be named "Failsafe Graphic Mode")
- will not log in default desktop, or desktop crashes, but
alternative to change desktop is in the login screen at the bottom left corner, but how many will click on barely visible text (kdm). This is good for release. Please make life of a tester easier, and provide list, not drop down menu,
- ...
what we need is *test* software. I'm ready to run any software on my computer, not involving install nor destroying the present config. Soe could be used with current openSUSE install, others on boot only.
there was a beginning on this respect to send hardware config, but it was so confusing I don't even know what was sent
What do we have to test, in the beginning?
* All the specific suse things: mostly called YaST or SaX
* kde/gnome integration
for all this, specific test should be done, specially for all the new stuff nobody know else than the developpers, so script tests or test paper sheets and online forms
jdd
-
jdd