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

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

Summary: Remove CVS/GIT from the list of available Wine versions
           Product: WineHQ Bugzilla
           Version: unspecified
          Platform: Other
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P2
         Component: bugzilla-unknown
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]

With time it becomes very hard to track down to which Wine snapshot the bug
belongs. CVS/GIT tag is confusing, see for instance the bug 12358.

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

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

--- Comment #1 from Austin English   2008-04-22 01:05:52 ---
(In reply to comment #0)
> With time it becomes very hard to track down to which Wine snapshot the bug
> belongs. CVS/GIT tag is confusing, see for instance the bug 12358.

Many bugs may then get filed under the previous wine version. How about
removing CVS/GIT but adding the new releases in advance?

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

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

--- Comment #2 from Dmitry Timoshkov   2008-04-22 01:25:27 ---
(In reply to comment #1)
> Many bugs may then get filed under the previous wine version.

Not really, cvs/git version is still "the previous wine version" with
some patches on top of it.
> How about
> removing CVS/GIT but adding the new releases in advance?

That would add even more confusion IMO.

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

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

--- Comment #3 from Austin English   2008-04-22 01:55:10 ---
(In reply to comment #2)
> (In reply to comment #1)
> > Many bugs may then get filed under the previous wine version.
>
> Not really, cvs/git version is still "the previous wine version" with
> some patches on top of it.

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

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

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

--- Comment #4 from James Hawkins   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.

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

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

--- Comment #5 from Lei Zhang   2008-04-22 03:07:11 ---
I'm all for it, but can we do it without flooding ~3000 emails into people's
inboxes?

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

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

--- Comment #6 from James Hawkins   2008-04-22 03:13:13 ---
824 to be exact, and we can do like we did before when removing obsolete
components: correct 100 per day or so until there are no more CVS/GIT versions.

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

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

--- Comment #7 from Vitaliy Margolen   2008-04-22 09:33:27 ---
Please don't remove cvs/git version. Also I think this discussion should be
taken to wine-devel.

What should be done is:
1. Leave old bugs alone or modify them case-by-case
2. All bugs with "cvs/git" version from now on can be filed on the development
branch between releases only.
3. After the next release, if the bug is still present, modify version to that
release. Of course no modifying of old bugs.

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

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

--- Comment #8 from Dmitry Timoshkov   2008-04-22 09:47:23 ---
(In reply to comment #7)
> - Leave old bugs alone or modify them case-by-case
> - All bugs with "cvs/git" version from now on can be filed on the development
>
> branch between releases only.
> 3. After the next release, if the bug is still present, modify version to that
> release. Of course no modifying of old bugs.

The problem is that there is no such a thing as CVS/GIT Wine version
for the bug report purposes, every next commit makes this tag invalid.

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

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

--- Comment #9 from Austin English   2008-04-22 11:32:59 ---
(In reply to comment #5)
> I'm all for it, but can we do it without flooding ~3000 emails into people's
> inboxes?

Can we disable e-mail when doing mass edits, along with allowing one/few people
on to do those edits?

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

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

Dan Kegel  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #10 from Dan Kegel   2008-04-24 05:47:26 ---
You can't make decisions like this just on bugzilla or irc, you
have to involve the mailing list, too.

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

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

--- Comment #11 from Dmitry Timoshkov   2008-06-16 21:58:47 ---
It seems there were no (strong) objections to this.
Is it possible to do that along with the 1.0 release? Any bugzilla admins?

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

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

--- Comment #12 from Dan Kegel   2008-06-16 22:10:45 ---
I haven't seen any substantive discussion of this on wine-devel.
Did I miss something?

In any case, I strongly object until I detect consensus.12728

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

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

--- Comment #13 from Dmitry Timoshkov   2008-09-28 16:04:20 ---
At WineConf we discussed this problem with interested people. Alexandre doesn't
really care about the Wine version bug field, and others are not against the
removal of CVS/GIT version tag.

So, the first thing to do is make sure that no new bugs are reported with
CVS/GIT
version tag. Next thing is somehow get rid of existing CVS/GIT bug reports, by
probably setting the version field to "unspecified" and ask the bug reporter to
set the correct version.

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

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

--- Comment #14 from Dmitry Timoshkov   2008-10-14 22:56:25 ---
Question to the bugzilla admins: Is it possible to remove the CVS/GIT
version from the list of available versions at the time a new bug is being
created? That way we will be sure that no new bugs with that tag will be
filed.

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

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

Danny Rawlins  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #15 from Danny Rawlins   2008-11-29 01:41:41 ---
Why not have the GIT tag and then input the commit as "git describe" reports?

This way it would be much easier to track down what commit the bug was tested
against.

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

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

--- Comment #16 from Dmitry Timoshkov   2008-11-29 22:56:15 ---
(In reply to comment #15)
> Why not have the GIT tag and then input the commit as "git describe" reports?

How can you see it will fit in the Version field of the bug report?
> This way it would be much easier to track down what commit the bug was tested
> against.

'wine --version' says it clear enough what version is it.

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

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

Dmitry Timoshkov  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED

--- Comment #17 from Dmitry Timoshkov   2009-01-20 12:07:19 ---
Fixed. Thanks Austin!

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

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

Dmitry Timoshkov  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #18 from Dmitry Timoshkov   2009-01-20 12:07:36 ---
Closing.