On Mon, 2007-04-23 at 06:30 +1000, Registration Account wrote:
For those people out there testing the next version of open suse 10,3 - could some great degree of testing involve testing the Product in a upgrade situation rather than a New installation. After I upgraded 10,1 to 10,2 RC I came across more bugs to the extent that the upgrade ability could only be rated as beta. I begin reporting upgrade bugs, however due to the enormity and frequent comment by suse.de (Then you should not buy new software). I was not prepared to waste more of my time. I always buy boxed software and my only plea for Alpha 10,3 that a great deal of testing is done via an upgrade (not clean) installation I have been testing software (given most of my earlier life's experience was with large Main Frame installations), and latter PC operating systems. The upgrade path for all New software application development is always the most difficult to achieve. As an active tester of RC software I need to gain some personal confidence that upgrade-ability has been tested by a few more dedicated other
Kind Regards and Good Morning 06:30 GMT+10 Scott
This is what I'm doing with my laptop, going through the upgrade cycle and reporting problems. The main problem I have reported is the upgrade _not_ ising mt /boot partition during the upgrade process and leaving me with a system that cannot boot without manual intervention. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org