Hello,
I thought I'd try to start a discussion to try to encourage changes in the bug tracking, but it would both require agreement and someone (else) who could physically make the changes.
Is it me or is our bug tracking database not really working the way it should?
Firstly I'd like to thank Tony - he seems to do a lot of maintaining of the bug database and deserves a lot of credit. Until I started looking through them and monitoring the bug mailing list, I didn't realize how much he did.
<blush> ah shucks </blush>
[snip]
Suggestions....
1. I would like to get implemented an AUTOMATIC timeout on the bug reports. If they are inactive for eg. 4 months then an automatic update is added to them asking to try latest cvs and confirm the problem still exists. If the problem is not updated within a month, the bug report gets automatically closed with a specific code (eg. CLOSED/inactivity).
I have looked at this and it is not possible to do this without drastically altering (forking) bugzilla. We can however get a list of bugs that have not had any activity for any length of time you want.
http://bugs.winehq.org/buglist.cgi?&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&field0-0-0=delta_ts&type0-0-0=lessthan&value0-0-0=2004-08-30
I have looked into having a resolution "abandoned" and that should be possible to do without forking bugzilla "Too Much".
2. I would like a clear way to identify if the problem can be reproduced with **free** downloadable software, eg a demo, freeware, shareware etc. This should be searchable for people wanting a quick bug fix
Search for Keyword "Download" I have been very thorough and "To The Best Of My Knowledge" anthing that has a download (demo, freeware shareware etc) is marked as such.
3. I would like there to be a transition from an initial state before being accepted, which basically allows rejection of a bug report if there is not enough information in it. Unfortunately someone would have to actively do this, so this would be a very had one to achieve.
This would require major changes to Bugzilla, and I do not, at the moment, want to start forking.
4. I would also like a bug fixing period of time, when all wine developers
are encouraged to work on bugs for eg. one day a month.
Interestingly, even though most people seem to end up working in a
particular area they may not handle bugs in that area (probably because they
don't check for them!). How many of the wine developers would consider
allocating time once a month (even if its just an hour!) to look at a bug
report, perhaps try it or go back asking for appropriate traces etc.
Pretty Please....!
--
Tony Lambregts
