Re: [QGIS-Developer] How long before closing an issue on "lack of feedback"?

2018-08-15 Thread Jürgen E . Fischer
Hi Matthias, On Tue, 14. Aug 2018 at 11:21:38 +0200, Matthias Kuhn wrote: > * Disable the stack when pdb are not installed > * Add some guidelines on issue reporting (as stated by Jonathan) > * Allow opening a new ticket and searching for identical reports to link to * Disable submission if

Re: [QGIS-Developer] How long before closing an issue on "lack of feedback"?

2018-08-14 Thread Nyall Dawson
On Tue, 14 Aug 2018 at 19:01, Jonathan Moules wrote: > > Hi Nyall, > > Looking at this from another angle (and being aware I know nothing of > the QGIS code-base) - to me at least that would suggest that maybe it's > worth improving the crash dumps so that they're better able to be used > as a

Re: [QGIS-Developer] How long before closing an issue on "lack of feedback"?

2018-08-14 Thread Paolo Cavallini
On 08/14/2018 11:21 AM, Matthias Kuhn wrote: > > Hi all, > > Can a new state "feedback required" be introduced (emphasis on > required) which then can be closed automatically if no feedback is > provided? This state would be set by humans when it's clear at the > time of setting the state that

Re: [QGIS-Developer] How long before closing an issue on "lack of feedback"?

2018-08-14 Thread Giovanni Manghi
> I agree in general, but there's a lot of tickets recently with just a > crash dump (with no clues in the dump) and no further info about how > to reproduce the crash or what triggered it. These reports don't have > *any* value on their own. > > Nyall By the way, since log we have also a

Re: [QGIS-Developer] How long before closing an issue on "lack of feedback"?

2018-08-14 Thread Matthias Kuhn
Hi all, Can a new state "feedback required" be introduced (emphasis on required) which then can be closed automatically if no feedback is provided? This state would be set by humans when it's clear at the time of setting the state that the ticked not only *would like to have* but actually *does

Re: [QGIS-Developer] How long before closing an issue on "lack of feedback"?

2018-08-14 Thread Jonathan Moules
Hi Nyall, Looking at this from another angle (and being aware I know nothing of the QGIS code-base) - to me at least that would suggest that maybe it's worth improving the crash dumps so that they're better able to be used as a stand-alone debugging thing that doesn't require user

Re: [QGIS-Developer] How long before closing an issue on "lack of feedback"?

2018-08-14 Thread Paolo Cavallini
On 08/14/2018 02:23 AM, Nyall Dawson wrote: > On Mon, 13 Aug 2018 at 18:11, Paolo Cavallini wrote: >> I agree, better be conservative. Furthermore, not always lack of feedback >> means an issue is not valid. I'd be against automatically closing the issues >> without further verification. > I

Re: [QGIS-Developer] How long before closing an issue on "lack of feedback"?

2018-08-13 Thread Nyall Dawson
On Mon, 13 Aug 2018 at 18:11, Paolo Cavallini wrote: > > I agree, better be conservative. Furthermore, not always lack of feedback > means an issue is not valid. I'd be against automatically closing the issues > without further verification. I agree in general, but there's a lot of tickets

Re: [QGIS-Developer] How long before closing an issue on "lack of feedback"?

2018-08-13 Thread Giovanni Manghi
> Gosh, 258 waiting for feedback! > > I'll have a look during the HF, thanks. what is the surprise here? is a "normal" number for our bug tracker, and in fact I usually use the dev meetings as occasion to make large cleanups of the tickets in feedback status. -- G --

Re: [QGIS-Developer] How long before closing an issue on "lack of feedback"?

2018-08-13 Thread Paolo Cavallini
Gosh, 258 waiting for feedback! I'll have a look during the HF, thanks. On 08/13/2018 11:13 AM, Luigi Pirelli wrote: > I agree with 30 days, Paolo the feedbak filter is already > available https://issues.qgis.org/projects/qgis/issues?query_id=112 > > Luigi Pirelli > >

Re: [QGIS-Developer] How long before closing an issue on "lack of feedback"?

2018-08-13 Thread Luigi Pirelli
I agree with 30 days, Paolo the feedbak filter is already available https://issues.qgis.org/projects/qgis/issues?query_id=112 Luigi Pirelli ** * LinkedIn: https://www.linkedin.com/in/luigipirelli *

Re: [QGIS-Developer] How long before closing an issue on "lack of feedback"?

2018-08-13 Thread Giovanni Manghi
> What's an "acceptable" amount of time between adding a question to a > ticket/marking as "feedback" before closing that issue as "Closed due > to lack of feedback"? > > Is 14 days sufficient? Hi Nyall, the official number is 15 days, but in reality in my personal effort to keep the tracker

Re: [QGIS-Developer] How long before closing an issue on "lack of feedback"?

2018-08-13 Thread Paolo Cavallini
I agree, better be conservative. Furthermore, not always lack of feedback means an issue is not valid. I'd be against automatically closing the issues without further verification. I'm available to help checking, maybe creating a view of tickets needing a check could be useful. All the best.

Re: [QGIS-Developer] How long before closing an issue on "lack of feedback"?

2018-08-13 Thread Alessandro Pasotti
I would suggest 30 days, people might be so lucky to have their holidays last longer than two weeks. On Mon, Aug 13, 2018 at 2:23 AM, Nyall Dawson wrote: > Quick question re closing issues on redmine: > > What's an "acceptable" amount of time between adding a question to a > ticket/marking as

[QGIS-Developer] How long before closing an issue on "lack of feedback"?

2018-08-12 Thread Nyall Dawson
Quick question re closing issues on redmine: What's an "acceptable" amount of time between adding a question to a ticket/marking as "feedback" before closing that issue as "Closed due to lack of feedback"? Is 14 days sufficient? Nyall ___