Hi everyone, I have recently been doing a lot of testing for * radeonhd - the os-ATI driver (upstreams, solely status report for OS) * the package management (zypper, YaST) * interested in testing Apparmor & SELinux; own development: checkroot Besides this I file most bug reports on diverse issues grub, bluetooth pairing, NTP, flashplayer for OS (OpenSuSE) - every problem that I encounter myself with Linux or that I am asked for by friends. Formerly I have been doing a lot of testing for KDE3; all of it at bugs.kde.org. However I have never really started to file reports for KDE4 because I thought that there would be simply too much to do and kept waiting for it to improve. As things are now there will still be a KDE3 repo for 11.2 (https://features.opensuse.org/306733), but it won`t be officially supported so I guess there is little sense in filing bug reports for KDE3. Regarding Gabriel Francos suggestion to report bugs for KDE/Gnome, I wanna recommend posting all of them upstreams and to only open up reports for OS if something heavily annoys or can not be done in time. As far as I am informed Novell only has 4 full time employees on KDE (Stephan Binner, Luboš Luňák, Dirk Mueller, Will Stephenson) - 20 testers for 4 developers will be too much! Regarding test for wireless networking I would greatly appreciate the support of kwlan, my favourite GUI-tool. However the last time kwlan has worked for me was OpenSuSE 11.0 (Bug 537159) so that I am directly using wpa_supplicant now. Initially I have been collecting some links for our test-work at opensuse.org/developer which however now has been replaced by a more comprehensive site. Nonetheless I personally prefer having the bare links (faster, more clear). That is why I have now put them online on my hompage: http://suse.elstel.com or www.elstel.com/suse - njoy. Regards, Elmar Am 10.09.2009 14:45, schrieb Spencer French:
Considering images for m7 should be around now/soon I was wondering what other members of the team thought our plan should be for this far along in the dev cycle?
And also what testing preferences each member has as well as available hardware so we can all have a rough idea of each others work flow.
I have 2 desktop machines both x86/64 as well as a macbook pro (early 2009) and a newish dell laptop, so I can do resume/suspend testing of those models. As far as preference I am really interested in the kde desktop/yast/zypper and xorg, although of course I will help with anything I can.
Also just as a heads up at work I will be posting from spf@varndean.ac.uk and at home from spencerpaulfrench@gmail.com.
Please consider the environment, only print out this email if absolutely necessary This email, together with any attachments, (the document) is for the exclusive use of the addressee(s). Any other distribution, use or reproduction of the document without the sender's prior consent is unauthorised and strictly prohibited. If you have received this document in error please notify the sender, by email or by telephone immediately and remove the message from your computer without making any copies. It is possible for data conveyed by email to be deliberately or accidentally intercepted or corrupted. For this reason, in communicating solely by email, Varndean College is unable to accept any responsibility for any breaches of confidence which may arise through the use of this medium. Varndean College will not accept any liability for contractual commitments made by individuals employed by Varndean College outside the scope of our business. Varndean College, Surrenden Road, Brighton, East Sussex, BN1 6WQ Tel: 01273 508011 Fax: 01273 542950 For further information on Varndean College, please visit our web site at http://www.varndean.ac.uk
-- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-testing+help@opensuse.org