On Sat, Jan 24, 2009 at 8:29 AM, Alexandre Julliard julliard@winehq.org wrote:
http://bugs.winehq.org/show_bug.cgi?id=17112 Should we make that a release criterion?
I don't think so, getting access to that info is troublesome, and we can't easily trigger new test runs. We don't want to have the release block on something that we don't control. Of course that doesn't mean we shouldn't fix the issues...
Actually, they do provide a way to trigger new test runs, we just don't do it yet.
Maybe once we have that set up, and have the data being pulled down into a publicly accessible report, maybe we can think of it as a release criterion.