Hi! My proposal: e) a reminder at major version + automated closing of bug report after first major.maintenance version if a reminder is last comment (which means no activity)
This will give bugs cleaning every 6 months. Not a bad deal... Most of bugs in NEEDINFO state are dead ends. Reporters in general think that people who triage are LO experts in every way. A reminder text should convince them, that the easier STR the better. Even very complicated issue can be reproduced with a "download'n'run" test case attached . BTW: I really liked graphics made by one reporter in bug https://bugs.freedesktop.org/show_bug.cgi?id=51162. IMHO all this should include also UNCONFIRMED bugs (many are dead ends too). I see bug reporting in this project not like "file and forget" process. Reminder text should encourage the reporter to get involved a little bit more, as he is an expert about reported bug, at least confirming it with latest major version. Also having a subpage for dealing with UNCONFIRMED or NEEDINFO bugs in Bugzilla would make life easier. Such page is available for instance in bmo (bugzilla.mozilla.org). Link: https://bugzilla.mozilla.org/page.cgi?id=triage_reports.html. Source is available at: http://bzr.mozilla.org/bmo/4.0/annotate/head:/extensions/BMO/template/en/default/pages/triage_reports.html.tmpl In short (their implementation): - Show UNCONFIRMED bugs with: [Product] [Component] - Comment: -- where the last commenter: is the reporter, does not have canconfirm, is [set user] -- where the last comment is older than: 30/60/90 days, one year, the date [set date] I played with it for a while and it is very friendly, especially for unexperienced Bugzilla users. In our version this should support UNCONFIRMED and NEEDINFO statuses and maybe reminder IDs, to browse the bugs before the next step (if one is concerned that important issues will be closed). It would be a great companion for triage marathons. Best regards. P.S. Everything has to be done to not repeat last incident with 3 or 4 messages added to selected issues. This was PITA for everyone. -- View this message in context: http://nabble.documentfoundation.org/Libreoffice-qa-Stagnant-NEEDINFO-bugs-tp4032113p4032419.html Sent from the QA mailing list archive at Nabble.com. _______________________________________________ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/