[Qgis-developer] Ticket cleanup after 2.0 release

Paolo Cavallini cavallini at faunalia.it
Mon Sep 9 05:47:00 PDT 2013

Hash: SHA1

Il 09/09/2013 14:01, Matthias Kuhn ha scritto:
> +1, I also like this idea.
> I would also like to reintroduce the idea of auto-closing tickets which 
> are in "Feedback" state for more than 2 weeks to keep the count low in 
> the future. Issues in "Feedback" state should be treated as "cannot be 
> solved with the current amount of information" and therefore shouldn't 
> be crowding the overview of active tickets until somebody provides the 
> missing bits.

Hi Pirming,
thanks for raising the issue. I'd be a bit careful about autoclosing. Tickets are a
huge source of knowledge about the program, often are opened as placeholder not to
forget missing function that we'll deal with, sooner or later, etc.
Besides that, users will sometimes take this as impolite, or think that we are trying
to hide problems, and refrain from getting involved with the project.
Me and Giovanni Manghi have dealt with (and opened[0]) many hundreds of tickets, and
I think nothing can replace careful consideration.
Having said that, I agree that if a ticket has no feedback for weeks, and is probably
a local issue, is better be closed.
Please do some careful simulation, checking the likely results, before acting.
This is by no means a secondary issue, as it involves our public image, and the
relations with our community.

All the best.

- -- 
Paolo Cavallini - Faunalia
Full contact details at www.faunalia.eu/pc
Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/calendario
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Icedove - http://www.enigmail.net/


More information about the Qgis-developer mailing list