[Bug 12728] Remove CVS/GIT from the list of available Wine versions

wine-bugs at winehq.org wine-bugs at winehq.org
Tue Apr 22 02:04:28 CDT 2008


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





--- Comment #4 from James Hawkins <truiken at gmail.com>  2008-04-22 02:04:28 ---
(In reply to comment #3)
> Right, but if I file a new bug for today's git, what would I label it as?
> wine-0.9.60 (it's not present there), CVS/GIT (removed), wine 0.9.61 (bug may
> be fixed by the time it's released).
> 

The answer is that you should file a current bug as the latest released
version.  The only way the bug can not be in that release is if the bug is a
regression wihch happened after the release.  In this special case, the
reporter will provide the commit id anyway, making the point moot.  The latest
release should be used to mean "release X plus commits before release X + 1 is
released."

> > 
> > > How about
> > > removing CVS/GIT but adding the new releases in advance?
> > 
> > That would add even more confusion IMO.
> > 
> Also a possibility, but we need to account for the case of bugs filed between
> release versions. Maybe a checkbox for git version, i.e., a bug filed on
> today's git would be listed as:
> 
> version: wine 0.9.60
> CVS/GIT: Yes
> 

That adds no useful information, just like the current CVS/GIT version label.


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