Hello, on Dienstag, 22. April 2008, Stephan Kulow wrote:
Beta1 is out and we see a lot of testing by a lot of you, many thanks for that. You can see the status of it in the list of most annoying bugs - not too bad, not too good either :)
I'd call the status quite good for a beta1 - at least for my usecases.
But I want to stress an important page, that Holgi was so nice to put together: the list of implemented features:
http://en.opensuse.org/Testing:Features_11.0
Why is this important? Because these features are often the reason for changes that cause bugs and as such are the central thing to test for new products. So beside your usual "this is what I'm doing with it" testing, it would be perfect if everyone could look at some.
The list is also great to answer the question "What's new in 11.0?" :-)
For details how we think it could be done, see the text on the page:
If you want to help testing, select the feature you want to test, edit this page and set it's "Testing Result" to "running" when starting the tests. ... If you are unable to finish the test, please reset the status from "running" to "idle".
Lazy people could also skip the "running" status and only set the status to "passed" or "failed" ;-) I'd like to propose that people should sign off the test result with their username ("--~~~~"). Advantages: - you know who has run a test and can ask for details, if necessary (try to find out after 40 edits when no username is stated... ;-) - maybe two persons running the test get different results. With the username added, everybody could add "his" result. Oh, and if a test failes, a link to the bugreport ("{{bug|123456}}") should be added. (Wiki page not changed yet - I'd like to hear some feedback first.)
Thanks a lot for your support. Please note that this is the first time we're doing it this way. Hopefully we'll have better tools for future versions, so we'll gladly hear your feedback on what works and what doesn't.
It was already said that a wiki page with about 200 items is too large. What about using the old betatestdb.suse.de for this? I think it should work for this usecase. I'd like to add another issue: Some of the features lack a useful description - take "Easy-to-use time/date applet needed (Feature No: 4134)" as an example. The only thing I can see is that it is desktop-related (what a surprise...), but the description is empty. Therefore it's impossible to comment on it if I don't know what it is about. I guess the page was auto-generated from FATE (which is OK in general, I don't want to force anybody to do it manually) - but please go through the page and add some details in cases like described above. One more: Some features include links to bugzilla.suse.de which are redirected to bugzilla.novell.com. Unfortunately the redirect leads to the wrong page. http://bugzilla.suse.de/show_bug.cgi?id=34654 redirects to https://bugzilla.novell.com/index.cgi?id=34654 but should go to https://bugzilla.novell.com/show_bug.cgi?id=suse34654 (yes, the "suse" part in the id is correct - AFAIK all bugs that were in bugzilla.suse.de got an alias "suse<original bug number>".) Oh, and I have just set two features to "passed" :-) Regards, Christian Boltz -- vi-Befehle sind sogar relativ einfach zu merken. Wenn man einmal weiß, was dw db de d) d( d} d{ dd d^ d$ d0 dG sowie cw und yw machen, dann weiß man auch, was cb ce c) c( c} c{ cc c^ c$ c0 cG sowie yb ye y) y( y} y{ yy y^ y$ y0 yG machen. [Bernd Bordesser in suse-linux] --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org