http://bugs.winehq.org/show_bug.cgi?id=17831
Summary: Autoclose ? Product: WineHQ Bugzilla Version: unspecified Platform: Other OS/Version: other Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: bugzilla-unknown AssignedTo: wine-bugs@winehq.org ReportedBy: cngnome@gmail.com
Now,
I hope this is the right list to log proposals for the bugzilla. If not, please instruct me of the correct approach.
I have been updating tickets, not touched for 3 months and browsing a lot of more of them. I have found a trend, that most of the low activity items are pretty much impossible to test for one of the following reasons.
1. The purpose of the program or issue is not stated and application is not in apps db. If a program is not in English, it is pretty hard to figure out what it does. And if the program is not in my scope of expertice - for example a scientific matrix program, then I don't have an idea what is the problem. A short note of the purpose would help.
2. There is no link to demo or example code. No instructions of how to compile the code. It is pretty impossible to figure out the issue.
3. There are no steps how to repeat it. For example I was looking a polish program. I had no idea of the logic or what it does because I don't understand Polish. A set of steps to dummies would help, for example: 1. execute this command, 2. press this button having this label etc. and then what happends.
4. Logger had lost interest on it. Or maybe the owner no longer has the program or has moved to other programs.
So many of the issues with above problems had been open for 2-7 years. In most cases the links no longer worked, programs had been updated and moved and original contacts where not there.
What I propose, is that all bugs missing the info and no updates would be automatically closed after three months. This would reduce the issues to something that could be solved by almost 50% - yesterday wine had 1980 open tickets with 781 items not touched for 3 months and 76 not touched for 6 months. Maybe a warning mail to logger after two months, two and half months, just before close and then autoclose. After which you could log a new request, pointing to old ticket ID and provision of the information of above with latest build.
With this process we testing volunteers could easily find the right test cases that would have the greatest benefit to wine developers community. Wine can never be 100% windows, but this would help to focus on the most important development items.
http://bugs.winehq.org/show_bug.cgi?id=17831
--- Comment #1 from Austin English austinenglish@gmail.com 2009-03-23 16:29:01 --- This is already done. I do it on a regular basis, haven't in the past couple weeks. Current policy is that if a bug has no activity for 3 months, and no download available, that we 'ping' the bug (you'll probably see a lot of 'Is this still an issue in current (1.1.X or newer) wine?). If 3 months more go by and no response (or a question was asked/information requested, and there is no response), the bug is closed as abandoned.
Bugs WITH a download are the tricky ones. For those, I usually wait til I have time to kill and test them myself (6 months inactivity). If the download link is busted, I remove the keyword and request for the reporter to retest and update the url. If in 3 months it isn't, then it's closed.
Now if more volunteers would check those old bugs with downloads, that would help...
FWIW, here's my abandoned query (currently 71, I'll probably ping them tomorrow): http://bugs.winehq.org/buglist.cgi?query_format=advanced&short_desc_type...
(I keep the search saved as 'abandoned' in bugzilla saved searches).
Here's the old + download (currently 75): http://bugs.winehq.org/buglist.cgi?query_format=advanced&short_desc_type...
I'm n
http://bugs.winehq.org/show_bug.cgi?id=17831
Tomasz Sałaciński tsalacinski@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |tsalacinski@gmail.com
--- Comment #2 from Tomasz Sałaciński tsalacinski@gmail.com 2009-03-24 10:15:16 --- (In reply to comment #0)
Which Polish program you are talking about? Which bug? I can translate you everything you need.
I've been downloading a lot of apps and posting comments on bugs, but believe me it takes a lot of time. I work for an ISP, so my connection at home is around 40mbps and I have no problem in downloading software, but hunting and reporting such bugs can take a LONG time. Maybe credit all people who are doing this, like for example a subpage Wine Testers or Wine BugHunters with names on it. Users without knowledge in C would be able to contribute and could motivated to do so.
http://bugs.winehq.org/show_bug.cgi?id=17831
--- Comment #3 from Austin English austinenglish@gmail.com 2009-03-24 11:07:11 --- (In reply to comment #2)
I've been downloading a lot of apps and posting comments on bugs, but believe me it takes a lot of time. I work for an ISP, so my connection at home is around 40mbps and I have no problem in downloading software, but hunting and reporting such bugs can take a LONG time. Maybe credit all people who are doing this, like for example a subpage Wine Testers or Wine BugHunters with names on it. Users without knowledge in C would be able to contribute and could motivated to do so.
A wikipage with tips on how to do so, etc. would be good. See: http://wiki.winehq.org/Bugs http://wiki.winehq.org/BugzillaTriage
http://bugs.winehq.org/show_bug.cgi?id=17831
--- Comment #4 from CN Gnome cngnome@gmail.com 2009-03-24 14:18:12 --- Regarding #1.
I used the link you gave on forum item http://forum.winehq.org/viewtopic.php?t=2655
It says : Here's a list of bugs (292 as of January 16, 2009) that have a download available, but haven't been checked on in the last 3 months.
I used the link on it and it gave me all old bugs instead the old ones having valid download. The link from that sticky mail is different the one you gave on this ticket. If I click on the link from forum I get 795 hits and if the one here in this ticket then 75 hits. This 795 caused me to log this ticket as I wondered how come there are so many tickets without useful download links or information. Now that I know better, I will focus to the narrowed list.
Would it be possible to put them both to forum item or fix the one there to point to ones that have no valid download ? Maybe someone else has also tried it and has given up after seeing all of them and having to find out that they cannot test them ?
---
Regarding #2 Polish program : http://bugs.winehq.org/show_bug.cgi?id=6278
But np; I guessed as much that when you press the last item on left hand menu, it must be exit and yes, it crashed :)
I just wanted to point out that if the program is not in English, it is pretty hard sometimes to know what to do. Ok, I can use google translate but the results are sometimes amusing ;)
http://bugs.winehq.org/show_bug.cgi?id=17831
--- Comment #5 from Tomasz Sałaciński tsalacinski@gmail.com 2009-03-27 14:59:49 --- Regarding comment #3:
There should be an information before posting the bug that if the program isn't in English user should provide few steps on where to click to reproduce the bug - or maybe WNE should find few people that are able to speak Polish, Spanish, Portugese, French, Russian, Italian etc. I saw a bug written in Russian - I know that these strange letters don't tell you anything, but it's still a bug. Someone should just translate it (I can read russian alphabet, but I understand it in 30%-40%).
And I think that proposal made by CN Gnome is right. WINE shouldn't keep old bugs forever. There should be a warning email sent to reporter that the bug is going to be closed unless he will confirm it with the newest WINE release. If the developer won't update it in 2 weeks, bug should be closed as INVALID.
http://bugs.winehq.org/show_bug.cgi?id=17831
--- Comment #6 from Austin English austinenglish@gmail.com 2009-03-27 15:47:57 --- (In reply to comment #5)
Regarding comment #3:
There should be an information before posting the bug that if the program isn't in English user should provide few steps on where to click to reproduce the bug
Yes, that probably should be done. Bugzilla's source is here: http://source.winehq.org/git/bugzilla.git/?a=shortlog
if you'd like to make a patch.
And I think that proposal made by CN Gnome is right. WINE shouldn't keep old bugs forever. There should be a warning email sent to reporter that the bug is going to be closed unless he will confirm it with the newest WINE release. If the developer won't update it in 2 weeks, bug should be closed as INVALID.
We don't already. But closing a bug just because it's old doesn't make sense. Some bugs we know aren't fixed, and are perfectly valid to keep open (implementing directplay, iPod support, etc.). Bugs with downloads can be tested by anyone. Bugs with no downloads, after not being active for 6 months are closed (albeit not automatically, I've got a pulse). I fail to see a real problem here...can you please explain what's wrong with the current system?
http://bugs.winehq.org/show_bug.cgi?id=17831
--- Comment #7 from Jeff Zaroyko jeffz@jeffz.name 2009-03-27 16:39:21 --- (In reply to comment #6)
(In reply to comment #5)
Regarding comment #3:
There should be an information before posting the bug that if the program isn't in English user should provide few steps on where to click to reproduce the bug
Yes, that probably should be done. Bugzilla's source is here: http://source.winehq.org/git/bugzilla.git/?a=shortlog
if you'd like to make a patch.
The 'New' bug page links to the Bug reporting guidelines on the wiki http://http://wiki.winehq.org/Bugs, so it would be more appropriate to add such instructions there rather than edit bugzilla itself.
http://bugs.winehq.org/show_bug.cgi?id=17831
--- Comment #8 from Austin English austinenglish@gmail.com 2009-03-27 17:06:49 --- (In reply to comment #7)
(In reply to comment #6)
(In reply to comment #5)
Regarding comment #3:
There should be an information before posting the bug that if the program isn't in English user should provide few steps on where to click to reproduce the bug
Yes, that probably should be done. Bugzilla's source is here: http://source.winehq.org/git/bugzilla.git/?a=shortlog
if you'd like to make a patch.
The 'New' bug page links to the Bug reporting guidelines on the wiki http://http://wiki.winehq.org/Bugs, so it would be more appropriate to add such instructions there rather than edit bugzilla itself.
I think a note about writing bugs in English is perfectly acceptable in the bulleted list. The others in the wiki, yes.
http://bugs.winehq.org/show_bug.cgi?id=17831
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #9 from joaopa jeremielapuree@yahoo.fr 2012-05-13 17:23:46 CDT --- Can this bug be closed?
http://bugs.winehq.org/show_bug.cgi?id=17831
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |WONTFIX
--- Comment #10 from Austin English austinenglish@gmail.com 2012-05-13 17:29:51 CDT --- (In reply to comment #9)
Can this bug be closed?
It's not going to happen on an automated basis, so sure.
http://bugs.winehq.org/show_bug.cgi?id=17831
Jerome Leclanche adys.wh@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED CC| |adys.wh@gmail.com
--- Comment #11 from Jerome Leclanche adys.wh@gmail.com 2012-05-13 21:46:57 CDT --- Closing.
-
wine-bugs＠winehq.org