[Bug 15419] Test Data reports should include wine stable versions (i.e. 1.0, 1.2...) and not just recent betas

wine-bugs at winehq.org wine-bugs at winehq.org
Fri Dec 19 16:12:26 CST 2008


http://bugs.winehq.org/show_bug.cgi?id=15419





--- Comment #31 from Ted Hansen <tedhansen at sasktel.net>  2008-12-19 16:12:25 ---
(In reply to comment #27)
> 
> Reopening. I think we need to leave 1.0.1 and mark it as stable. We may already
> do this, but the discussion doesn't make this clear.

One more time...would not establishing the practise of accepting test results
using the current stable (whatever version it be at the time) or anything newer
in the AppDb (not in Bugzilla) solve this?  

In reply to Comment  #25 From Vitaliy Margolen 2008-12-19 13:58:32  

>Regardless, the AppDB change was made to encourage people to use latest
>available Wine version(s). Having someone use 1/2+ year old or known broken
>version and submit test results that this app or that app doesn't work >doesn't really help. 

What if the test results are good...ie the app does work? Then not accepting
the test results just means that there is no information at all for the
potential user.

If the results indicate problems, then the user/tester should be encouraged to
upgrade but if all is well there should be no need for the user to have to
upgrade (or downgrade to stable) to "fix" something which is not broken.

>Considering those versions will not be fixed....

The purpose of the AppDb should be to inform potential users of how an app may
be expected to perform under wine, not to inform developers of bugs in wine
that need to be addressed. That is for Bugzilla, where it IS appropriate to
demand testing with the latest beta.


-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.



More information about the wine-bugs mailing list