http://bugs.winehq.org/show_bug.cgi?id=30150
Bug #: 30150 Summary: Disprencies in results Product: Wine Version: 1.4 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: butraxz@gmail.com Classification: Unclassified
The policy of bugzilla here states that issues later than 180 days with no activity should be first noted and then closed as abandoned if no reply is given.
If you query for bugs older than 180 days, this is true:
http://bugs.winehq.org/buglist.cgi?chfieldto=Now&query_format=advanced&a...
0 results.
However, if you take a date ranged query and examine individual issues, then you notice that this rule does not work in practice.
In this example take all open issues from 2006:
http://bugs.winehq.org/buglist.cgi?query_format=advanced&type0-1-0=lesst...
For example bug 5552 was updated, according entries, the last time more than a year ago.
However, it was modified in 2011-11-23 when a component was changed by a wine maintainer/developer.
The conclusion: The policy, that states that bugs should closed if there has been no activity for 6 months, does not work in practice because changes in components by maintainers are recorded as changes to bugs, whereas imho only logger and solver changes should qualify for changes. Therefore a lot of old bugs that should be marked as abandoned, but are just sticking in bugzilla forever, because 6 moth query is hiding them from helping hands. Investigation of the bug db shows a lot of cases like that.
http://bugs.winehq.org/show_bug.cgi?id=30150
Dan Kegel dank@kegel.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dank@kegel.com
--- Comment #1 from Dan Kegel dank@kegel.com 2012-03-12 11:58:57 CDT --- I suspect you used the wrong query the first time.
http://bugs.winehq.org/buglist.cgi?query_format=advanced&field0-0-0=days... finds 3942 open bugs older than 180 days.
So, invalid?
http://bugs.winehq.org/show_bug.cgi?id=30150
Dmitry Timoshkov dmitry@baikal.ru changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID
--- Comment #2 from Dmitry Timoshkov dmitry@baikal.ru 2012-03-12 12:03:14 CDT --- Nothing to fix in Wine.
http://bugs.winehq.org/show_bug.cgi?id=30150
Jerome Leclanche adys.wh@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED CC| |adys.wh@gmail.com Component|-unknown |bugzilla-unknown Version|1.4 |unspecified Product|Wine |WineHQ Bugzilla
--- Comment #3 from Jerome Leclanche adys.wh@gmail.com 2012-03-12 12:09:32 CDT --- Bugzilla bug. Closing.
http://bugs.winehq.org/show_bug.cgi?id=30150
--- Comment #4 from Austin English austinenglish@gmail.com 2012-03-12 13:34:21 CDT --- The process is not automatic, I typically search for those old bugs when I have free time and then check when the last comment was made.
Unfortunately, bugzilla doesn't allow searching when the last _comment_ was made, only when the last _change_ was made, which is often a component/keyword change, or a cc change.
-
wine-bugs＠winehq.org