draft Call for Testing

[Dan Kegel]

On Tue, May 6, 2008 at 8:19 AM, Adam Petaccia <adam at tpetaccia.com> wrote:
>  > 4. For each app you test, add a test report into Wine's AppDB.
>
>  I'd explicitly state something about reporting bugs for things that
>  don't work. It should be obvious, but being explicit rarely hurts. As I
>  tell my friends who refuse to file bugs: "They can't fix it if they
>  don't know its broke".

Yeah.   But I'd rather not scare them with bugzilla, so how about this:

4. For each app you test, add a test report into Wine's AppDB.
Since you're only testing apps that were rated as platinum,
it should work perfectly, even for people who don't know a
commandline from a kumquat.
If it doesn't work perfectly from start to finish, rate it no higher
than gold.  Now, if this was just a misrated application, you're
done.  But if you can verify that it actually worked great in an
earlier version of wine, you've found a regression!  In that
case, please post a message whose subject starts with 'regression:'
in the wine forum (or the wine-users mailing list), or file a bug
at bugs.winehq.org.

Now, that text is too long, but you get the idea.  How's it sound now?