[Bug 17831] New: Autoclose ?

[wine-bugs at winehq.org]

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 at winehq.org
        ReportedBy: cngnome at 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.


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