New core testing team

newer
Re: [opensuse-testing] New core...

older
Re: [opensuse-testing] New core...

Spencer French

10 Sep 2009 10 Sep '09

12:45

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

Show replies by date

Gabriel Franco

10 Sep 10 Sep

14:36

2009/9/10 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

Hi Spencer, I have 1 laptop x86/x64, an EeePC 1000h and an Aigo MID P8861H I think that the first item the Testing team need to come up with is the definition of the main areas we are going to focus for our testing and define sub-teams for each of the areas based on members preferences I think that we need to come up with a Test Plan / Cases for 2 main scenarios: - KDE Desktop - Gnome Desktop We need to define what to test and how to test the main applications provided on both desktop solutions like browser, e-mail client, file manager, yast, communication (IM and IRC), network management (WI-FI, ETH, PPP, VPN) and so on. For that we need to analyze what is already available as test cases on testopia and fill up the missing parts. Maybe we should try setting up a Team Meeting to get to know every member and come up with the first plan and objectives for the team. What do you think? Best, -- Gabriel Fróes Franco Software Architect Zend Certified Engineer - PHP5 Sun Java Certified Programmer - Java 5 openSUSE Member openSUSE Testing Core Team Discover Freedom =============== openSUSE Linux http://www.opensuse.org OpenOffice.org http://www.openoffice.org Netbeans IDE http://www.netbeans.org Please consider the environment before printing this e-mail. -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-testing+help@opensuse.org

Kayo Hamid

14:54

For me, testing is a complex term to define. I will work on the core of openSUSE, and not on the last release, to give more performance for him, like the project for reducing the boot time, http://en.opensuse.org/Boottime/Boot_time. I have some ideas for it and i known what i need to do, so i will show for the group the results soon. On Thu, Sep 10, 2009 at 10:36 AM, Gabriel Franco wrote:

...

2009/9/10 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.

...

Hi Spencer,

I have 1 laptop x86/x64, an EeePC 1000h and an Aigo MID P8861H

I think that the first item the Testing team need to come up with is the definition of the main areas we are going to focus for our testing and define sub-teams for each of the areas based on members preferences

I think that we need to come up with a Test Plan / Cases for 2 main scenarios:

- KDE Desktop - Gnome Desktop

We need to define what to test and how to test the main applications provided on both desktop solutions like browser, e-mail client, file manager, yast, communication (IM and IRC), network management (WI-FI, ETH, PPP, VPN) and so on.

For that we need to analyze what is already available as test cases on testopia and fill up the missing parts.

Maybe we should try setting up a Team Meeting to get to know every member and come up with the first plan and objectives for the team.

What do you think?

Best,

-- Kayo Hamid Fontinhas - kayohf@gmail.com openSUSE Ambassadors - Brazil openSUSE Testing Core Team -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-testing+help@opensuse.org

Gabriel Stein

15:08

Well.. I was planning to test all installation process, testing all options and after go to desktop test. For installation, I will test automated installation, without changing options, just accepting it, after doing some customization, and after test "experienced" installation. To desktop tests, I will like to test a basic office suite: Desktop with firefox, konqueror, mail clients, and office working, without crashes. I know, which firefox and openoffice, for example, isn't developed by openSUSE Project, but its really important these integration for a workstation. I can test it with gnome and kde. I saw the last email talking about desktop tests too... I think which we can do 2 major teams to testing: Installation and Desktop. There are a lot of choices and ways to install... and maybe bugs too. For desktop? Well... a riot from choices and setup, to test and check. IMHO - I'm thinking about important topics to test Installation Test Team -- Test all installation process: - Test different installation options, until the first installation screen - text or graphical - Languages support: For example, german, english, spanish, portuguese and french. Yes, there's a lot of languages also!; - Keyboard layout support: To test the main layout offered; - Test YaST repositories and hardware detection in the first detection screen; - Test automated installation -- extensive tests. Pay a lot of attention to usability, for final and low experienced users; - Test Partitioner - LVM, ext3, ext4, mounting NFS and FAT32 and NTFS partitions; - Test YaST packager - Choose, solving dependencies.... - Test Security/Auth - Choosing different methods, different passwords and so on; - Test Network Configuration - DHCP, Static IP.... and many different setups; - Test YaST updates; - Test final hardware detection, as VideoCard... - And finally: test the final result after the first GNOME/KDE boot. Desktop Test Team -- Test all desktop(as a workstation/media center/basic server): - Test KDE initial boot and first setup - Test GNOME initial boot and first setup - Test KDE Language support and Keyboard Layout; - Test GNOME Language support and Keyboard Layout; For both: - Test Hardware - Sound, Video, Bluetooth devices; - Test firefox integration; - Test file manager(Nautilus/Dolphin); - Test automount; - Test network configuration; - Test openoffice integration; - Test IM integration; - Test Mail Client integration; We don't need an official desktop or installation test team. We can't decide by ourselves, and choose and area to test and fill bugzilla with our tests, and of course, there are many tests to do which Holger already created! If a team finish desktop or installation tests, can help another team to finish also. Is not a competition, its a better organization for tests and easier to concentrate in a few and exhausted tests. Is it a good idea or not? Sorry, I'm entering just now in testing mailing list, but its my 2 cents of contribution. All the best. 2009/9/10 Gabriel Franco :

...

2009/9/10 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

Hi Spencer,

I have 1 laptop x86/x64, an EeePC 1000h and an Aigo MID P8861H

I think that the first item the Testing team need to come up with is the definition of the main areas we are going to focus for our testing and define sub-teams for each of the areas based on members preferences

I think that we need to come up with a Test Plan / Cases for 2 main scenarios:

- KDE Desktop - Gnome Desktop

We need to define what to test and how to test the main applications provided on both desktop solutions like browser, e-mail client, file manager, yast, communication (IM and IRC), network management (WI-FI, ETH, PPP, VPN) and so on.

For that we need to analyze what is already available as test cases on testopia and fill up the missing parts.

Maybe we should try setting up a Team Meeting to get to know every member and come up with the first plan and objectives for the team.

What do you think?

Best,

-- Gabriel Fróes Franco Software Architect Zend Certified Engineer - PHP5 Sun Java Certified Programmer - Java 5 openSUSE Member openSUSE Testing Core Team

Discover Freedom =============== openSUSE Linux http://www.opensuse.org

OpenOffice.org http://www.openoffice.org

Netbeans IDE http://www.netbeans.org

Please consider the environment before printing this e-mail. -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-testing+help@opensuse.org

-- /\ Gabriel Stein gabrielstein@gmail.com +55 51 9953 1337 -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-testing+help@opensuse.org

Spencer French

15:33

Yes I think we should arrange a meeting maybe on irc?, so we can all exchange some ideas and really start moving since we are at m7. Maybe some things we could touch on are, Areas of interest(Multimedia, kde, gnome performance etc) Hardware available Times/schedules of each member The breaking down of testing into teams (I like the desktop, installation and maybe server groups) etc But thinking about it we probably should inform everyone of our schedules now so we can see when everyone is available. Most days I work 11:30am - 7:30pm so i am mainly free 8 - 10:20 (11:30 if you count just email), and then from 4:30 onwards as work is slower then, all that is GMT mon - fri and I all completely free most weekends. One last thing I really like Gabriel Stein post that think that's a good place to start a discussion from. Spencer Paul French Technical Support Engineer Email: spf@varndean.ac.uk Extension: 115 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

Gabriel Stein

15:43

Well.. I totally agree with a IRC meeting. I`m free from monday to thursda(all afternoons) and some mornings too, for example monday and thursday. GMT -3 Timezone. Best, 2009/9/10 Spencer French :

...

Yes I think we should arrange a meeting maybe on irc?, so we can all exchange some ideas and really start moving since we are at m7. Maybe some things we could touch on are,

Areas of interest(Multimedia, kde, gnome performance etc) Hardware available Times/schedules of each member The breaking down of testing into teams (I like the desktop, installation and maybe server groups)

etc

But thinking about it we probably should inform everyone of our schedules now so we can see when everyone is available.

Most days I work 11:30am - 7:30pm so i am mainly free 8 - 10:20 (11:30 if you count just email), and then from 4:30 onwards as work is slower then, all that is GMT mon - fri and I all completely free most weekends.

One last thing I really like Gabriel Stein post that think that's a good place to start a discussion from.

Spencer Paul French Technical Support Engineer

Email: spf@varndean.ac.uk Extension: 115

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

-- /\ Gabriel Stein gabrielstein@gmail.com +55 51 9953 1337 -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-testing+help@opensuse.org

Marco Poletti

16:14

I am free in this period: from 7:00 to 10:00 (morning) and from 12:00 to 17:00 (afternoon) in most days this period. I am busy on these days: Friday 11 (tomorrow) morning Tuesday 15 (next Tuesday) afternoon I live in UTC+2, I've converted it to UTC for clarity. Marco Poletti -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-testing+help@opensuse.org

Gabriel Franco

16:23

2009/9/10 Marco Poletti :

...

I am free in this period: from 7:00 to 10:00 (morning) and from 12:00 to 17:00 (afternoon) in most days this period. I am busy on these days:

Friday 11 (tomorrow) morning Tuesday 15 (next Tuesday) afternoon

I live in UTC+2, I've converted it to UTC for clarity.

Marco Poletti -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-testing+help@opensuse.org

Hi all, I usually have some free time during the week from 18:00 to 22:00, and all day on weekends. I live in UTC-3 - Brazil. Maybe we shoudl go and create a wiki page for the team where we can centralize the info to make it ease to find a timeframe that works for everyone. I'm unable do to so now since I'm at work with limited access to internet. Best, -- Gabriel Fróes Franco Software Architect Zend Certified Engineer - PHP5 Sun Java Certified Programmer - Java 5 openSUSE Member openSUSE Testing Core Team Discover Freedom =============== openSUSE Linux http://www.opensuse.org OpenOffice.org http://www.openoffice.org Netbeans IDE http://www.netbeans.org Please consider the environment before printing this e-mail. -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-testing+help@opensuse.org

Gabriel Stein

17:09

2009/9/10 Gabriel Franco :

...

2009/9/10 Marco Poletti :

...
I am free in this period: from 7:00 to 10:00 (morning) and from 12:00 to 17:00 (afternoon) in most days this period. I am busy on these days:

Friday 11 (tomorrow) morning Tuesday 15 (next Tuesday) afternoon

I live in UTC+2, I've converted it to UTC for clarity.

Marco Poletti -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-testing+help@opensuse.org

Hi all,

I usually have some free time during the week from 18:00 to 22:00, and all day on weekends.

I live in UTC-3 - Brazil.

Maybe we shoudl go and create a wiki page for the team where we can centralize the info to make it ease to find a timeframe that works for everyone.

I don't know if is possible. But if you can, do it. Its a better idea to organize time, meetings and tasks(completed or not completed and responsible). I was wondering about a timesheet too, to evaluate how many hours we spend to test and how many bugs will be discovered in these testing hours.

...

I'm unable do to so now since I'm at work with limited access to internet.

Best,

-- Gabriel Fróes Franco Software Architect Zend Certified Engineer - PHP5 Sun Java Certified Programmer - Java 5 openSUSE Member openSUSE Testing Core Team

Discover Freedom =============== openSUSE Linux http://www.opensuse.org

OpenOffice.org http://www.openoffice.org

Netbeans IDE http://www.netbeans.org

Please consider the environment before printing this e-mail. -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-testing+help@opensuse.org

-- /\ Gabriel Stein gabrielstein@gmail.com +55 51 9953 1337 -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-testing+help@opensuse.org

Gabriel Franco

17:14

2009/9/10 Gabriel Stein :

...

2009/9/10 Gabriel Franco :

...
2009/9/10 Marco Poletti :

...
I am free in this period: from 7:00 to 10:00 (morning) and from 12:00 to 17:00 (afternoon) in most days this period. I am busy on these days:

Friday 11 (tomorrow) morning Tuesday 15 (next Tuesday) afternoon

I live in UTC+2, I've converted it to UTC for clarity.

Marco Poletti -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-testing+help@opensuse.org

Hi all,

I usually have some free time during the week from 18:00 to 22:00, and all day on weekends.

I live in UTC-3 - Brazil.

Maybe we shoudl go and create a wiki page for the team where we can centralize the info to make it ease to find a timeframe that works for everyone.

I don't know if is possible. But if you can, do it. Its a better idea to organize time, meetings and tasks(completed or not completed and responsible). I was wondering about a timesheet too, to evaluate how many hours we spend to test and how many bugs will be discovered in these testing hours.

It is possible. I'll work on it as soon as I get home and post the link here.

...

...
I'm unable do to so now since I'm at work with limited access to internet.

Best,

-- Gabriel Fróes Franco Software Architect Zend Certified Engineer - PHP5 Sun Java Certified Programmer - Java 5 openSUSE Member openSUSE Testing Core Team

Discover Freedom =============== openSUSE Linux http://www.opensuse.org

OpenOffice.org http://www.openoffice.org

Netbeans IDE http://www.netbeans.org

Please consider the environment before printing this e-mail. -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-testing+help@opensuse.org

-- /\ Gabriel Stein gabrielstein@gmail.com +55 51 9953 1337 -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-testing+help@opensuse.org

-- Gabriel Fróes Franco Software Architect Zend Certified Engineer - PHP5 Sun Java Certified Programmer - Java 5 openSUSE Member openSUSE Testing Core Team Discover Freedom =============== openSUSE Linux http://www.opensuse.org OpenOffice.org http://www.openoffice.org Netbeans IDE http://www.netbeans.org Please consider the environment before printing this e-mail. -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-testing+help@opensuse.org

Dave Plater

16:37

On 09/10/2009 05:33 PM, Spencer French wrote:

...

Yes I think we should arrange a meeting maybe on irc?, so we can all exchange some ideas and really start moving since we are at m7. Maybe some things we could touch on are,

Areas of interest(Multimedia, kde, gnome performance etc) Hardware available Times/schedules of each member The breaking down of testing into teams (I like the desktop, installation and maybe server groups)

Hi, I'm Dave Plater I have one x86_64 system that runs factory that I use for day to day work. Most of my bug reporting has been against zypper / yast installation system and kde but I use firefox and thunderbird extensively. My working hours are very erratic and include weekends sometimes the easiest times for me to attend an irc meeting would be Tuesday or Thursday from 18:30 GMT but I could find a Saturday or Sunday afternoon free, my timezone is GMT +2 Regards Dave P -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-testing+help@opensuse.org

Larry Finger

16:38

Spencer French wrote:

...

Yes I think we should arrange a meeting maybe on irc?, so we can all exchange some ideas and really start moving since we are at m7. Maybe some things we could touch on are,

Areas of interest(Multimedia, kde, gnome performance etc) Hardware available Times/schedules of each member The breaking down of testing into teams (I like the desktop, installation and maybe server groups)

I reside in Central US - GMT -5 when daylight saving is in place. I'm retired and normally available from 15:00 - 3:00 GMT on weekdays; however, I'm traveling at the moment and will not be on that schedule until Monday. I will be reading E-mail today. If an IRC meeting is arranged, please post a link to the archive so that I will be able to see what was said. Larry -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-testing+help@opensuse.org

Jürgen Radzuweit

17:47

Hi All, an IRC chat would be great, so we can discuss how to proceed and were we should set our focus. For proceeding I would suggest, that we create a list of hardware as already suggested and structure it according to the hardware support list. So we get a good overview of which areas of hardware is covered and which is not. We can put this list than on the Wiki so everybody has access to it. The other thing I suggest is that we start with the two test plans holgi has provided so far. As I have seen It's quit a lot of tests to run. If we have done so we get a good "feeling" of how to proceed and fill the gaps. I don't expect to be fully "operational" on the testing issue with a new team in the next two or three releases. We also should considere to create a third test plan covering this hardware issue during installation. From my experience it's always the most annoying part of the installation and the most users of Liinux want to know if their hardware works with the new release. Another thing I would suggest is that we go through the bug list of a new release and compile tests for the most often appearing issues. So we learn from the community. And the last for now, we should think of how to automate tests, because testing a operating system with all it's applications and options is quite a big task. Cheers and happy testing Jürgen Am Donnerstag, 10. September 2009 17:33:56 schrieb Spencer French:

...

Yes I think we should arrange a meeting maybe on irc?, so we can all exchange some ideas and really start moving since we are at m7. Maybe some things we could touch on are,

Areas of interest(Multimedia, kde, gnome performance etc) Hardware available Times/schedules of each member The breaking down of testing into teams (I like the desktop, installation and maybe server groups)

etc

But thinking about it we probably should inform everyone of our schedules now so we can see when everyone is available.

Most days I work 11:30am - 7:30pm so i am mainly free 8 - 10:20 (11:30 if you count just email), and then from 4:30 onwards as work is slower then, all that is GMT mon - fri and I all completely free most weekends.

One last thing I really like Gabriel Stein post that think that's a good place to start a discussion from.

Spencer Paul French Technical Support Engineer

Email: spf@varndean.ac.uk Extension: 115

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

-- ------------------------------------------------------ Jürgen Radzuweit Am Steinebrück 23 40589 Düsseldorf Telefon : 0211/788 5115 Mobil : 0172/210 4989 EMail : juergen@radzuweit.eu -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-testing+help@opensuse.org

Gabriel Stein

18:01

Am 10. September 2009 14:47 schrieb Jürgen Radzuweit :

...

Hi All, an IRC chat would be great, so we can discuss how to proceed and were we should set our focus. For proceeding I would suggest, that we create a list of hardware as already suggested and structure it according to the hardware support list. So we get a good overview of which areas of hardware is covered and which is not. We can put this list than on the Wiki so everybody has access to it. The other thing I suggest is that we start with the two test plans holgi has provided so far. As I have seen It's quit a lot of tests to run. If we have done so we get a good "feeling" of how to proceed and fill the gaps. I don't expect to be fully "operational" on the testing issue with a new team in the next two or three releases.

We also should considere to create a third test plan covering this hardware issue during installation. From my experience it's always the most annoying part of the installation and the most users of Liinux want to know if their hardware works with the new release.

Well... I agree. We have a lot of tests which Holgi already provided, I`m just wondering to do extensively tests, more than provided by Holgi. But also, is so important to work with pre-configured tests in Bugzilla. For hardware tests, a list in a wiki, with all hardware tested and compatibility is a great idea!

...

Another thing I would suggest is that we go through the bug list of a new release and compile tests for the most often appearing issues. So we learn from the community.

And the last for now, we should think of how to automate tests, because testing a operating system with all it's applications and options is quite a big task.

Cheers and happy testing

Jürgen

Am Donnerstag, 10. September 2009 17:33:56 schrieb Spencer French:

...
Yes I think we should arrange a meeting maybe on irc?, so we can all exchange some ideas and really start moving since we are at m7. Maybe some things we could touch on are,

Areas of interest(Multimedia, kde, gnome performance etc) Hardware available Times/schedules of each member The breaking down of testing into teams (I like the desktop, installation and maybe server groups)

etc

But thinking about it we probably should inform everyone of our schedules now so we can see when everyone is available.

Most days I work 11:30am - 7:30pm so i am mainly free 8 - 10:20 (11:30 if you count just email), and then from 4:30 onwards as work is slower then, all that is GMT mon - fri and I all completely free most weekends.

One last thing I really like Gabriel Stein post that think that's a good place to start a discussion from.

Spencer Paul French Technical Support Engineer

Email: spf@varndean.ac.uk Extension: 115

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

-- ------------------------------------------------------ Jürgen Radzuweit Am Steinebrück 23 40589 Düsseldorf

Telefon : 0211/788 5115 Mobil : 0172/210 4989 EMail : juergen@radzuweit.eu -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-testing+help@opensuse.org

-- /\ Gabriel Stein gabrielstein@gmail.com +55 51 9953 1337 -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-testing+help@opensuse.org

Holger Sickenberg

11 Sep 11 Sep

12:35

Hi Jürgen,

...

[...]

We also should considere to create a third test plan covering this hardware issue during installation. From my experience it's always the most annoying part of the installation and the most users of Liinux want to know if their hardware works with the new release.

If you need an additional Test Plan I can create that for you. Just let me know

...

[...]

Best wishes, Holgi -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-testing+help@opensuse.org

Jürgen Radzuweit

12 Sep 12 Sep

05:05

Hi Holgi, ok thanx I will let you know if I need one. But for now I think we should run through the stuff you provided so far to see if it's usefull and get familiar with Testopia. BTW, do you have any idea of a roadmap and goals for the core testing team? Some sort of rough timeline and what to test would be a good idea, otherwise we do a lot of testing and have covered only a fraction of what was exepected (or the developer think of we should test). Is there a place where we can place some working documents? Because I would start with this hardware list. So many of the others have posted now what kind of hardware they have and I think someone should start to condense this information otherwise it's getting lost in the mailing list. Jürgen Am Freitag, 11. September 2009 14:35:57 schrieb Holger Sickenberg:

...

Hi Jürgen,

...
[...]

We also should considere to create a third test plan covering this hardware issue during installation. From my experience it's always the most annoying part of the installation and the most users of Liinux want to know if their hardware works with the new release.

If you need an additional Test Plan I can create that for you. Just let me know

...
[...]

Best wishes, Holgi

Holger Sickenberg

14 Sep 14 Sep

08:43

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Jürgen,

...

ok thanx I will let you know if I need one. But for now I think we should run through the stuff you provided so far to see if it's usefull and get familiar with Testopia.

BTW, do you have any idea of a roadmap and goals for the core testing team? Some sort of rough timeline and what to test would be a good idea, otherwise we do a lot of testing and have covered only a fraction of what was exepected (or the developer think of we should test).

Is there a place where we can place some working documents? Because I would start with this hardware list. So many of the others have posted now what kind of hardware they have and I think someone should start to condense this information otherwise it's getting lost in the mailing list.

There is already a wiki page at http://en.opensuse.org/OpenSUSE_Testing_Core_Team Files can be uploaded and (and linked in wiki page) at http://en.opensuse.org/Special:Upload Best wishes, Holgi -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAkquAiYACgkQ539IWoEy06XJJgCbBIejSJWTgUgNGsQYB/byPhpS zckAnjuWPrOp97MBVbvWJswKu2vQ5Bb7 =D4Hw -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-testing+help@opensuse.org

Atri

13 Sep 13 Sep

20:26

On Friday 11 September 2009 18:05:57 Holger Sickenberg wrote:

...

Hi Jürgen,

...
[...]

We also should considere to create a third test plan covering this hardware issue during installation. From my experience it's always the most annoying part of the installation and the most users of Liinux want to know if their hardware works with the new release.

If you need an additional Test Plan I can create that for you. Just let me know

...
[...]

Best wishes, Holgi

I request you to replicate the already existing plans (feature-testing and applications) for x86_64 architecture. Thanks -- Atri -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-testing+help@opensuse.org

Larry Finger

10 Sep 10 Sep

15:18

I think it is a good idea to establish our frame of reference for openSUSE testing. My main interest is in wireless networking. I have worked for several years as a member of the team that developed the reverse-engineered driver for Broadcom BCM43XX devices, and for the past two years, I have been on the RE side of the fence converting MIPS binary into "specifications", i.e. a set of "do this, then do that" lists. Wireless has long been a problem with Linux in general. One continually hears the complaint "Why doesn't it work the way Windows does?". The driver side of the equation is in pretty good shape with the development of the MAC layer and associated components. We do handle regulatory requirements and restrictions really well, which is very important as many wireless devices are operated outside the region encoded in their PROM. Another development is that manufacturers are contributing more to drivers. In particular, Intel and Atheros have sizable groups devoted to Linux drivers. Unfortunately, Broadcom is not among that group, but they do now offer a binary driver for their latest devices. It has a lot of faults, which is why the RE group is working hard to support the newer BCM devices. The area that needs watching and testing is NetworkManager, which is early in the development cycle (Version 0.7). With each new release, existing code is likely to break configurations that were working. On two recent occasions, once with 11.1 and once with 11.2, updates made it impossible to connect to an encrypted network. That situation is what I hope to catch before the updates are released. My hardware consists of an HP laptop winning x86_64 with 2 different mini-PCIe Broadcom wireless devices, a desktop also running x86_64, and an ancient Mtech laptop with the AMD version of an i586 CPU with two distinct Cardbus-based Broadcom devices. In addition, I have a Dell DW1450U device that uses p54usb as its driver, two Realtek USB wifi sticks - an RTL8187L and an RTL8187B, and two PCI-based Broadcom devices for the desktop. I hope that the efforts of this group will help to improve openSUSE. I started my Linux efforts with SuSE 6.4 and have been a user since. Larry -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-testing+help@opensuse.org

Gabriel Stein

15:39

2009/9/10 Larry Finger :

...

I think it is a good idea to establish our frame of reference for openSUSE testing.

My main interest is in wireless networking. I have worked for several years as a member of the team that developed the reverse-engineered driver for Broadcom BCM43XX devices, and for the past two years, I have been on the RE side of the fence converting MIPS binary into "specifications", i.e. a set of "do this, then do that" lists.

Wireless has long been a problem with Linux in general. One continually hears the complaint "Why doesn't it work the way Windows does?".

Brilliant! If you can help with this issue, will be a great step for openSUSE! Better compatibility with wireless device, for example Broadcom, which has a lot of problems.

...

The driver side of the equation is in pretty good shape with the development of the MAC layer and associated components. We do handle regulatory requirements and restrictions really well, which is very important as many wireless devices are operated outside the region encoded in their PROM. Another development is that manufacturers are contributing more to drivers. In particular, Intel and Atheros have sizable groups devoted to Linux drivers. Unfortunately, Broadcom is not among that group, but they do now offer a binary driver for their latest devices. It has a lot of faults, which is why the RE group is working hard to support the newer BCM devices.

The area that needs watching and testing is NetworkManager, which is early in the development cycle (Version 0.7). With each new release, existing code is likely to break configurations that were working. On two recent occasions, once with 11.1 and once with 11.2, updates made it impossible to connect to an encrypted network. That situation is what I hope to catch before the updates are released.

Yes, work with encrypted connections are so important! Did you created a bug report to NetworkManager too? NetworkManager to me is a problem too, because I can`t do last KDE version(KDE 4.3) work automatically with my own static ip configuration. If we can talk with NetworkManager team and also with openSUSE developer team, will be a great work!

...

My hardware consists of an HP laptop winning x86_64 with 2 different mini-PCIe Broadcom wireless devices, a desktop also running x86_64, and an ancient Mtech laptop with the AMD version of an i586 CPU with two distinct Cardbus-based Broadcom devices. In addition, I have a Dell DW1450U device that uses p54usb as its driver, two Realtek USB wifi sticks - an RTL8187L and an RTL8187B, and two PCI-based Broadcom devices for the desktop.

I hope that the efforts of this group will help to improve openSUSE. I started my Linux efforts with SuSE 6.4 and have been a user since.

Sincerely, its my main motivation too. I work with SuSE/openSUSE since 1999. And I think which since SuSE 6.4, we have a lot of success, improvements, and we will reach a perfect distro. Its all about motivation dude!

...

Larry

-- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-testing+help@opensuse.org

Best, -- /\ Gabriel Stein gabrielstein@gmail.com +55 51 9953 1337 -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-testing+help@opensuse.org

Larry Finger

16:31

Gabriel Stein wrote:

...

2009/9/10 Larry Finger :

...
I think it is a good idea to establish our frame of reference for openSUSE testing.

My main interest is in wireless networking. I have worked for several years as a member of the team that developed the reverse-engineered driver for Broadcom BCM43XX devices, and for the past two years, I have been on the RE side of the fence converting MIPS binary into "specifications", i.e. a set of "do this, then do that" lists.

Wireless has long been a problem with Linux in general. One continually hears the complaint "Why doesn't it work the way Windows does?".

Brilliant! If you can help with this issue, will be a great step for openSUSE! Better compatibility with wireless device, for example Broadcom, which has a lot of problems.

It is difficult without vendor support. Please specify the problems with Broadcom. I suspect I know most of them, but just in case.

...

...
The driver side of the equation is in pretty good shape with the development of the MAC layer and associated components. We do handle regulatory requirements and restrictions really well, which is very important as many wireless devices are operated outside the region encoded in their PROM. Another development is that manufacturers are contributing more to drivers. In particular, Intel and Atheros have sizable groups devoted to Linux drivers. Unfortunately, Broadcom is not among that group, but they do now offer a binary driver for their latest devices. It has a lot of faults, which is why the RE group is working hard to support the newer BCM devices.

The area that needs watching and testing is NetworkManager, which is early in the development cycle (Version 0.7). With each new release, existing code is likely to break configurations that were working. On two recent occasions, once with 11.1 and once with 11.2, updates made it impossible to connect to an encrypted network. That situation is what I hope to catch before the updates are released.

Yes, work with encrypted connections are so important! Did you created a bug report to NetworkManager too? NetworkManager to me is a problem too, because I can`t do last KDE version(KDE 4.3) work automatically with my own static ip configuration. If we can talk with NetworkManager team and also with openSUSE developer team, will be a great work!

The bugs have not been with NM as much as the API changing and openSUSE not following. I do, however, follow the NM mailing list and have filed bug reports with then and openSUSE. I can certainly explore your issue with them. In my own case, I don't use NM when I have a static IP. Larry -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-testing+help@opensuse.org

Gabriel Stein

17:15

2009/9/10 Larry Finger :

...

Gabriel Stein wrote:

...
2009/9/10 Larry Finger :

...
I think it is a good idea to establish our frame of reference for openSUSE testing.

My main interest is in wireless networking. I have worked for several years as a member of the team that developed the reverse-engineered driver for Broadcom BCM43XX devices, and for the past two years, I have been on the RE side of the fence converting MIPS binary into "specifications", i.e. a set of "do this, then do that" lists.

Wireless has long been a problem with Linux in general. One continually hears the complaint "Why doesn't it work the way Windows does?".

Brilliant! If you can help with this issue, will be a great step for openSUSE! Better compatibility with wireless device, for example Broadcom, which has a lot of problems.

It is difficult without vendor support. Please specify the problems with Broadcom. I suspect I know most of them, but just in case.

I know Larry. Sometimes vendor support isn't the best. But I think which you can guide us to discover these bugs, and we can do some documentation about it. For a distro user, its so important to know normal or expected errors running a final release. We can't be responsible for everything, but if we define and discover before users, shows confidence between Project and Testing Team.

...

...
...
The driver side of the equation is in pretty good shape with the development of the MAC layer and associated components. We do handle regulatory requirements and restrictions really well, which is very important as many wireless devices are operated outside the region encoded in their PROM. Another development is that manufacturers are contributing more to drivers. In particular, Intel and Atheros have sizable groups devoted to Linux drivers. Unfortunately, Broadcom is not among that group, but they do now offer a binary driver for their latest devices. It has a lot of faults, which is why the RE group is working hard to support the newer BCM devices.

The area that needs watching and testing is NetworkManager, which is early in the development cycle (Version 0.7). With each new release, existing code is likely to break configurations that were working. On two recent occasions, once with 11.1 and once with 11.2, updates made it impossible to connect to an encrypted network. That situation is what I hope to catch before the updates are released.

Yes, work with encrypted connections are so important! Did you created a bug report to NetworkManager too? NetworkManager to me is a problem too, because I can`t do last KDE version(KDE 4.3) work automatically with my own static ip configuration. If we can talk with NetworkManager team and also with openSUSE developer team, will be a great work!

The bugs have not been with NM as much as the API changing and openSUSE not following. I do, however, follow the NM mailing list and have filed bug reports with then and openSUSE. I can certainly explore your issue with them. In my own case, I don't use NM when I have a static IP.

Yes, for sure. Thanks by your help and attention! I will try to not use NM too.

...

Larry

Rajko M.

11 Sep 11 Sep

04:01

On Thursday 10 September 2009 07:45:49 Spencer French wrote:

...

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.

For hardware configuration and test results consider including smolt infrastructure in test team infrastructure. It is easier to run smolt, mark working and non working parts, and explain problems on smolt wiki, then to start from scratch. Using our wiki as a glue to link to different smolt profiles can save some time in test organization. IMHO, we would need wiki pages (topics) like: Test Team Members: simple list of members with links to equipment and test profiles, listing subgroups that have interest in particular type of testing Test Team Equipment and Profiles: simple list of equipment with links to smolt profiles (more details about hardware) and interest in testing (test profile) Testing Team Tests List of tests, common in any version, version specific, bug reports tests, etc. Test Results 11.2 main page as index of other pages (needs manual update), but this can be wiki category added to each of test result pages. Test Results 11.2/Test 1 <-- This from Holgi's list of tests and/or other tests that Team can come up with. The structure with one subpage for each test is required to have enough room for many testers and results. Also, there will be needed some pages with instructions for new tester, whom to contact (team head), where to find test plans, and what is the procedure. Did I miss something? (surely yes, but what?) -- Regards, Rajko People of openSUSE editor. Latest interviews: http://news.opensuse.org/category/people-of-opensuse/ About us: http://en.opensuse.org/People_of_openSUSE/About -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-testing+help@opensuse.org

Peter Czanik

07:29

Hello, 2009-09-10 14:45 keltezéssel, Spencer French írta:

...

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.

I'm S.u.S.E. user from 4.3 and tester from 5.x :-) For long my interest was desktop applications and some hw/installation. From the openSUSE 10.X series this shifted to hw/installation on PowerPC machines, of course reporting any other bugs I encountered. Also did SLES 10 PPC and 11 x86 tests, but that's another topic. Right now I'm downloading ARM packages from dl9pf's BS repository for a test and hoping to see a fully supported ARM port of openSUSE in the future. I have the following machines: - 1 self built Intel Core2Duo desktop with Nvidia 7600 - vmware workstation 6.X running on the above machine ;-) - 1 Dell Inspiron Mini 10v netbook (with a Broadcom wireless, which does not work on Linux even with Broadcom's own closed source driver, only from Windows) - 1 Pegasos PPC ( http://www.genesi-usa.com/products/opendesktop ) - 3 EFIKA PPC ( http://www.genesi-usa.com/products/efika/5200b ) - various Freescale PPC development systems (MPC8610, MPC5121), where I ported openSUSE (~hacked installer to work and provided a kernel, better than most Linux BSP's :-) ) I still use one of these to compile Packman packages for PPC... - 1 EFIKA MX development system (Freescale ARM iMX515: http://www.genesi-usa.com/products/efika ), where I already have a very basic openSUSE running - 1 Sheeva Plug (Marvell ARM:http://www.marvell.com/products/embedded_processors/developer/kirkwood/sheev... ) So, as you can see, I'm very interested in "alternative" hardware, where it is already a challenge to get something installed. So right now I'm mainly interested in the installer part. On the desktop side I'm interested in XFCE and KDE4. I work as sysadmin, so I also tend to test server applications. As sysadmin, I have time when there is planned maintenance / disaster at the moment :-) I added #opensuse-testing to my automatic channel list in Pidgin, where I think we should all be available. Bye, CzP -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-testing+help@opensuse.org

Elmar Stellnberger

12 Sep 12 Sep

08:11

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

Terje J. Hanssen

21:57

Spencer French wrote:

...

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.

Hi, I'm Terje J. Hanssen, Mo i Rana, Norway. * My Linux experience At home/HO, I've used SuSE since Professional v.9.0, all openSUSE 10.x and 11.x and to some degree SLED10-11. On our SOoffice we apply SLES10.x/OES2/NOWS with Xen on the server side, where I currently use openSUSE 11.1 on my workstation desktop. Initially I started with Unix SVR1 as a user and system administrator in our small firm since 1984, following up with Sparc/SunOS/Solaris since 1990. Windows use and integration has been a parallel/integrated part of this. * Previous testing experience Beta tested first Sun's Java Desktop/Linux based on SLE8.x. Later somewhat on openSUSE 10.x and more on openSUSE 11.0. My latest experience was as a beta tester on Novell SLED11. * Areas I'm interested in testing First of all I wish to test the components I use for my normal HO-Office setup and multiboot environment: - Gnome desktop (possibly some KDE4 and Goblin/Moblin later) - some YaST configurations - rdesktop/tsclient to W2k3, openVPN and NX clients - desktop hosting/virtualization on Xen/SUSE - some applications (Mozilla Firefox/Seamonkey/Thunderbird, OpenOffice, Gimp, Kino/Cinelerra) - possibly a later beta (in my office) with Novell Client, GroupWise client and a Cad system and a MFP network printer * Available hardware devices Two machines at home: - HP Compac 8710w mobile workstation w/BD-burner (64bit) - a K7 based stationary PC (old) (I've just installed openSUSE 11.2M7 x86_64 and i686 one these) - Epson scanner - digicam, HD camcorder, firewire HD recorder/disk I expect we still should post bug reports and RFEs on the normal Novell bugzilla for 11.2 (as before). Possibly discuss and refere to these bugs on this mailing list. To get test results confirmed on more hardware among test team members, possibly post test procedures to follow here on this list(?) Terje -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-testing+help@opensuse.org

Thomas Schulte

13 Sep 13 Sep

16:02

Hi, I'm Thomas Schulte from Essen, North Rhine-Westphalia, Germany. My first SuSE Linux version was 7.1, I think. After configuring my first apache webserver and beeing online for about 5 minutes (via modem and "every second billing") I knew that this would be the beginning of a great friendship. :-) My current hardware consists of * a desktop machine (AMD Athlon 64 X2 3800+) * an HTPC (Intel Celeron E1500) * an netbook (Asus EEE PC 1000H) * a brand new root-server (Intel Core i7-920) with VMware Server + VMs At the moment I'm interested in KDE desktop and FreeNX, because I'd like to work in a VM on my remote server to take advantage of it's power. :-) In times of not programming Java, I'm working on my mail-/webserver environment or I'm experimenting with KIWI and SuSE Studio to create a customized ThinClient system. In addition, I have a good knowledge about some server daemons like DHCP, DNS, Postfix, Cyrus IMAPd, Apach2, MySQL, ... My timezone is UTC +2 (Daylight Saving Time). At the moment I'm not sure where to start in this new group, but I think that an IRC meeting and (of course) this mailing list is going to organize the different options and tasks. :-) Regards, Thomas Am Thursday 10 September 2009 14:45:49 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

TooMany Secrets

19:24

On Sun, Sep 13, 2009 at 6:02 PM, Thomas Schulte wrote:

...

I'm Thomas Schulte from Essen, North Rhine-Westphalia, Germany.

Hi. My name is Manuel Trujillo, and I'm the SysAdmin dpt. chief from a company dedicated to a big on-line database of legal information. More than the 80% of all desktops are running openSUSE, and more than 95% of the more than 60 servers also run openSUSE. I think I could try to test apps like twinkle and ekiga (we work with a VoIP pbx). Also, if we can do it, other apps will be wellcome. Thank you very much. -- --------------------------------------------------------------------------------------- Have a nice day ;-) TooManySecrets /"\ ASCII Ribbon Campaign | FreeBSD Since 4.x \ / - NO HTML/RTF in e-mail | GNU/Linux Since 1994. X - NO Word docs in e-mail | OpenSUSE Member / \ - http://www.toomany.net --------------------------------------------------------------------------------------- -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-testing+help@opensuse.org

Bernhard M. Wiedemann

19:58

Hi, I'm Bernhard M. Wiedemann from Berlin, Germany. My first SuSE Linux was 6.1 in 1999 and I have had a lot of fun and done a lot of work on suse ever since then. My main systems are 2 Notebooks http://www.smolts.org/show?uuid=pub_c5345625-52df-4d29-9f31-acb6df810402 http://www.smolts.org/show?uuid=pub_318d5637-bf30-4b24-bfe0-ed6718e5fdcf and a Phenom X4 tower http://www.smolts.org/show?uuid=pub_9008bae4-6ab2-4a69-b889-3e0bbd32389f then there is my machine at work http://www.smolts.org/show?uuid=pub_114eb01a-53f1-4e0d-9491-d65c6117e046 and an Asus eeepc 900A netbook (currently running the pre-installed Xandros) Incidentally, I also got a brand new root-server (Intel Core i7-920) - but with kvm VMs, which happen to act strange with Milestone 7. I could do some testing on suspend-to-disk and suspend-to-ram which both have had their problems in the past, but are great if they work flawlessly on a notebook. It is just so much easier to open your notebook in the train, start working 2 seconds later and closing it when reaching your destination (not to mention the possible hundreds of days uptime). Additionally, I use KVM/VirtualBox to test something on my tower. Ciao -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-testing+help@opensuse.org

5342

Age (days ago)

5346

Last active (days ago)

List overview

Download

28 comments

17 participants

participants (17)

Atri
Bernhard M. Wiedemann
Dave Plater
Elmar Stellnberger
Gabriel Franco
Gabriel Stein
Holger Sickenberg
Jürgen Radzuweit
Kayo Hamid
Larry Finger
Marco Poletti
Peter Czanik
Rajko M.
Spencer French
Terje J. Hanssen
Thomas Schulte
TooMany Secrets