[prev in list] [next in list] [prev in thread] [next in thread] 

List:       wine-devel
Subject:    Dropping support for win2k in tests
From:       Jacek Caban <jacek () codeweavers ! com>
Date:       2015-09-25 16:05:15
Message-ID: 560570BB.9080002 () codeweavers ! com
[Download RAW message or body]

Hi all,

I mentioned the concern on WineConf already and we quickly decided to
not care about win2k during WineConf test session. But there is more to
that: do we want to drop win2k support in our tests.

I think we do. We have extra code to handle it all over tests codebase.
Those are mostly skip()s + broken()s because, well, we don't care about
win2k results. And if we don't care, then what's the point to bother and
do the extra work.

Stefan mentioned that ddraw has differences between win2k and newer
version. That's true for other libraries as well. I don't think that's
enough for the reason to keep win2k supported. A real case where test
results on win2k was useful lately would be. Do we have an example of a
real (not theoretical) use of win2k tests in recent Wine development?

Thanks,
Jacek


[prev in list] [next in list] [prev in thread] [next in thread]