murn,
do we have a policy for NEEDINFO bugs that are on the auto-reject list?
yesterday, i removed 364864 from the auto-reject list because it seemed
pretty useless to me to reject a *needinfo* bug with "only" 60 dups
which needs more info.
now we have 349697 (auto-reject && NEEDINFO) which could have been fixed
in SVN (both trunk and gtk-2-10 branch) by 396161.
what to do here?
i suggest to keep the auto-reject state, but edit the "Reason" field, so
we send out an email like
"Thanks for taking the time to report this crash. We hope that this
issue has been fixed by now, but need some confirmation from reporters
that run a current SVN version of gtk 2.10 or 2.11.
If you compile from SVN, we ask you to leave a comment on the bug
report."
comments (especially by guenther and bkor)?
otherwise i'll do this.
i also plan to take a look at the simple-dup-finder results for *closed*
bug reports that still get dups and would auto-reject them by adding a
reason ("this bug has been fixed! update!!"), like i did here:
http://bugzilla.gnome.org/show_bug.cgi?id=114425#c37
anyone contradicting?
andre
--
mailto:ak-47 gmx net | failed!
http://www.iomc.de/ | http://blogs.gnome.org/portal/aklapper
Attachment:
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil