-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi everybody,
openSUSE 11.3 Milestone 2 is official announced now. It is available at http://software.opensuse.org/developer
Please have a look at http://en.opensuse.org/Bugs:Most_Annoying_Bugs_11.3_dev before you start your installation.
Further information on testing are available at http://en.opensuse.org/Testing
I also attached the announcement mail from Henne.
Looking forward to your feedback.
Thanks, Holgi
Holger Sickenberg wrote:
Hi everybody,
openSUSE 11.3 Milestone 2 is official announced now. It is available at http://software.opensuse.org/developer
I occasionally have new machines to install or test or configure, and I usually try out whatever the latest opensuse milestone or build is. The thing is - yes, I can open bugreports but I will most probably not be able to follow up with any additional info as the machines will be in production or returned by the time somebody responds. So what is the best way to report feedback when I just want to fire and forget? (maybe it's not really very useful at all?)
/Per Jessen, Zürich
On Wed, 24 Feb 2010 08:54:07 +0100 Per Jessen per@computer.org wrote:
The thing is - yes, I can open bugreports but I will most probably not be able to follow up with any additional info as the machines will be in production or returned by the time somebody responds. So what is the best way to report feedback when I just want to fire and forget? (maybe it's not really very useful at all?)
Hi Per,
any kind of the feedback is useful and in all cases the best way is to use bugreports. Nobody is going to blame you for not having the HW anymore.
Have fun,
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi Per,
openSUSE 11.3 Milestone 2 is official announced now. It is available at http://software.opensuse.org/developer
I occasionally have new machines to install or test or configure, and I usually try out whatever the latest opensuse milestone or build is. The thing is - yes, I can open bugreports but I will most probably not be able to follow up with any additional info as the machines will be in production or returned by the time somebody responds. So what is the best way to report feedback when I just want to fire and forget? (maybe it's not really very useful at all?)
My suggestion is: create bug reports and try to add as much information to it (which makes sense, e.a. full hwinfo, YaST2 logs, X logs, etc.)
Best wishes, Holgi
-
Holger Sickenberg -
Per Jessen -
Vladimir Botka