Closing NEEDSINFO bugs after 30 days

[Harald Sitter]

On Mon, Nov 19, 2018 at 1:12 AM Myriam Schweingruber <myriam at kde.org> wrote:
>
>
>
> On Fri, 16 Nov 2018 at 14:22, Harald Sitter <sitter at kde.org> wrote:
>>
>> On Fri, Nov 16, 2018 at 2:16 PM Boudewijn Rempt <boud at valdyas.org> wrote:
>> >
>> > On vrijdag 16 november 2018 14:11:29 CET Harald Sitter wrote:
>> >
>> > > - human sets needsinfo
>> > > - 15 days pass: bot posts reminder
>> > > - reporter comments
>> > > - N days pass: bug gets automatically dropped back to whatever the
>> > > previous state was?
>> >
>> > Yes, that would be perfect! As far as I'm concerned, N can be 0 or 1.
>>
>> Cool. Should be easy to do.
>>
>> Any disagreements from the rest of the community?
>>
>> TLDR: if the original reporter comments on a needsinfo bug it gets
>> automatically switched back to whatever the state before needsinfo was
>
>
> It slightly disturbs my triaging routine, as I routinely check the NEEDSINFO I set within a month (and I have saved searches for this), so could "my" bugs be excluded, please? It is a really short time span, I always consider people to be away for longer than just two weeks (holidays, etc) which is very often the case. Some bug reports do answer on a regular basis, just noth within 2 weeks in all cases.

This is about the original NEEDSINFO discussion, not related to the
question I posed, is it?

If the timing seems unsuitable I'd like changing it discussed within
the bug squad. I am just the code monkey, in that capacity I'd like to
avoid a wall of conditions for every person doing bug triage.

HS