[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]

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





--- Comment #32 from Austin English <austinenglish at gmail.com>  2008-12-19 16:47:38 ---
(In reply to comment #31)
> (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?  

I agree with keeping the latest stable version, but NOT the versions in
between. We want the latest results in wine, be it from the stable branch or
the unstable branch. If distros are shipping the stable branch, fine. If
they're shipping unstable, they should be shipping recent versions, not
shipping 4 month old versions and calling it 'new'.

> 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.
> 

If the version tested is relatively recent at the time, it'll be accepted and
stay there for a while. E.g., if you tested 1.1.1 when it was new and submitted
results, they'd still be there. But if you wanted to do so now, there'd be
little point. It's not a stable release, and it's really outdated. Upgrade to
1.1.10 and submit your tests.

Bugzilla is not the appropriate place for a discussion. If you'd like to debate
this with me personally, feel free to e-mail me. Otherwise, wine-devel would be
more appropriate.

Long story short, in my view, for versions in AppDB we should have:
Unstable - Latest 5 or 6 releases, in descending order.
Stable - Latest release (1.0.1 in this case, 1.2.0 whenever that is)

Other versions should NOT be listed for NEW submissions. Any old test data, of
course, will remain, unless deleted by maintainers or admins.


-- 
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.