The changes you see were due to me. The Status change was a convenience to me
for follow up, but as noted, has caused alarm. My apologies for that. I am
already in process of sending updates and resetting the status, but am doing so
in blocks to not spam anyone. Give it a few days and all will
On Fri, Nov 16, 2018 at 10:37 AM Luigi Toscano wrote:
> Please disable it for now, or just enable it for projects who explicitly wants
> it for now.
As mentioned on IRC: everyone please note that unless a change was
made by bug-jani...@kde.org it was not actually done automatically (or
not that
On 16.11.2018 12:50, Boudewijn Rempt wrote:
-- and worse, it makes me hesitate to put bugs in the NEEDINFO state.
Worse. Bugs that never have been in NEEDSINFO seem to automatically get
this state after some time of inactivity now.
On vrijdag 16 november 2018 10:37:08 CET Luigi Toscano wrote:
> the (semi)automated process which pings and then closes NEEDINFO bugs was
> implemented, but I've noticed another policy which was never discussed (as
> far as I know) here: bugs opened for a while
>
> I disagree with this policy,
Luigi Toscano ha scritto:
Andrew Crouthamel ha scritto:
I've been spending a lot of time browsing, searching, and filtering our bugs
in Bugzilla. One of the areas I've found that could use improvement, are the
NEEDSINFO bugs. Often, bugs are placed into this status, either awaiting
additional
On Fri, 16 Nov 2018 at 10:37, Luigi Toscano
wrote:
> Andrew Crouthamel ha scritto:
> > I've been spending a lot of time browsing, searching, and filtering our
> bugs
> > in Bugzilla. One of the areas I've found that could use improvement, are
> the
> > NEEDSINFO bugs. Often, bugs are placed into
Andrew Crouthamel ha scritto:
I've been spending a lot of time browsing, searching, and filtering our bugs
in Bugzilla. One of the areas I've found that could use improvement, are the
NEEDSINFO bugs. Often, bugs are placed into this status, either awaiting
additional information or backtraces,
