Thanks for your reply Martin, which is for now the only one. ;-) Basically what you want to do is what each member of the "team" would have to do in my opinion. The other task for this group should be to collect information on HOW to do testing and reporting bugs correctly, which necessarily has to involve some Novell people at the beginning, so we can learn what they need and write it down in a non-technical form that can be understood by more users. Feel free to share your list ;-) Regards, A. Il giorno mar, 24/02/2009 alle 17.55 +0100, Martin Schlander ha scritto:
Mandag 23 februar 2009 19:33:42 skrev Alberto Passalacqua:
I have thought for quite some time to the idea of building a community-based openSUSE testing team
I'm not sure an organized team is necessary. But after the 11.1 fiasco, I plan to apply more of a systematic and methodic approach to testing personally.
Previously I would basically just test that installation and hardware support/detection worked on my machines - and not much more than that, taking for granted that basic everyday stuff would work and be tested by someone else.
But now I've started to compile a list of things I consider critical and my intention is to test everything in that list everytime. Basic things like cd- burning, kbluetooth, 1-click installation, updater applet, printing, home bank, wireless, multimedia, docx-documents etc.
Hopefully the recent steps taken to improve the factory experience will mean more and earlier testing. And hopefully for non-SLE-base releases there'll be less post-feature-freeze experimentation and feature development, than was the case for 11.1.
-- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org