Talkback versions of wine
Chris Morgan
cmorgan at alum.wpi.edu
Thu Oct 27 21:22:29 CDT 2005
A user sent this to the appdb mailing list. I thought the talkback idea was
an interesting one that we might want to consider now that we are nearing
1.0.
Chris
---------- Forwarded Message ----------
Subject: suggest Appdb
Date: Thursday 27 October 2005 10:02 pm
From: "Elektro Schock" <elektroschock at linuxmail.org>
To: appdb at winehq.org
"Email your suggestions for improving the AppDB"
Well,
1. what I would like to see are Wine talkback versions
a) terminal output + related app + wine version + other config
b) delete dublicates
c) automatical submission to a server
d) add to app specific database if not dublicate
Benefits:
* Wine developers are able to determine what console output is generated when
using the software * It is traceable what real applications will get
improved when a certain FIXME is fixed and what applications depend on a
bug. * app related bug reporting via automation
* it is possible to limit reporting to certain apps e.g. gold and silver apps
only or certain types of bugs and to set a time limit for the talkback
feature, so you get no old version reports. * you can determine what
applications were tried by users and whether problems still exist * bug
reporting becomes easier.
2. Where do I find documentation about the different kinds of wine bugs
reported at the console?
err
fixme
Unexpected calls
bugs invoking wine-dbg
etc.
When you run an application with you run into "bugs". But certainly there
often is no strict severity. What are severe errors that need to get
reported?
What are just unimplemented features?
I further assume that bugzilla FIXMEs are not the same as console output
FIXMEs
--
_______________________________________________
Check out the latest SMS services @ http://www.linuxmail.org
This allows you to send and receive SMS through your mailbox.
Powered by Outblaze
-------------------------------------------------------
More information about the wine-devel
mailing list