[Qgis-developer] bugs policy

[Tim Sutton]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Paolo Cavallini wrote:
> Hi all.
> I try to keep the (loooong) ticket queue tidy, removing duplicates,
> closing fixed bugs, etc. I think too many unverified bugs will distract
> the attention of developers, and will give a bad general impression of
> the whole project.
> I think it would be good to have a policy for closing non confirmed and
> obsolete bugs. If I cannot replicate the bug, I am asking the reporter
> to check them again against a new QGIS version, to provide additional
> info, or the data that caused the crash, etc.
> What should we do when the reporter does not reply, and the bus is
> apparently not replicable? I would be inclined to close it down after,
> say, a week; the reporter gets notified anyway, and (s)he can reopen the
> ticket at will.
> Any thoughts?
> All the best.

+1 from me

- --

Tim Sutton - QGIS Project Steering Committee Member (Release  Manager)
==============================================
Please do not email me off-list with technical
support questions. Using the lists will gain
more exposure for your issues and the knowledge
surrounding your issue will be shared with all.

Visit http://linfiniti.com to find out about:
 * QGIS programming and support services
 * Mapserver and PostGIS based hosting plans
 * FOSS Consulting Services
Skype: timlinux
Irc: timlinux on #qgis at freenode.net
==============================================

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkngeToACgkQqk07qZdiYjdlJgCgmqpCcDQcpsxYN03CFPdAQ4YK
YdAAoLACjFHUnT4k/JB2CEhrVzADXDSi
=Q0i9
-----END PGP SIGNATURE-----