Stop bugzilla bot from marking issues as "RESOLVED ARCHIVED".

Gregory Szorc gregory.szorc at gmail.com
Tue Jan 29 13:37:21 EST 2019


I generally agree: I view the existing behavior of marking bugs as ARCHIVED
RESOLVED as somewhat user hostile. I've received various complaints from
users over the years about this. It can come across that we don't care
about bug reports.

I do think that having a mechanism periodically make noise on a bug is
useful, as it can revive dormant bugs that slipped under the radar. But we
can do that without marking bugs as ARCHIVED RESOLVED.

Perhaps we could change the bot to leave a comment every N days unless
there is a keyword or whiteboard entry suppressing this behavior? If we
didn't have a way to suppress, I fear we'd just get bug spam from all
opened bugs all the time and nobody would pay attention to that fire hose.

On Tue, Jan 29, 2019 at 7:38 AM Pulkit Goyal <7895pulkit at gmail.com> wrote:

> Hey everyone,
>
> I am quite annoyed by the bugzilla bot marking inactive issues as RESOLVED
> ARCHIVED. Following are the reasons why I want the bot should be stopped to
> do that.
>
> 1) Handful of issues only live in a state of bot marking that as "resolved
> archived" and then author marking that as "CONFIRMED" again. This goes on
> until author of the issues decides to surrender. This is not a good UX.
>
> 2) Hides bugs. There are some existing bugs which are marked as "RESOLVED
> ARCHIVED" because nobody looked at them when they was filed. This does not
> mean that nobody will look at them or need them. Having a bug active helps
> in:
>   * Looking for existing bugs in a certain component. For example, I want
> to try narrow, and there are let's say 2 bugs related to narrow with
> "RESOLVED ARCHIVED" state, it won't be obvious for me to look for bugs in
> that state. Also I might hit the bug again in future.
>   * With programmes like summer of code, we have few new contributors
> coming every year. Or there are people who just want to contribute, having
> those bugs there might help to them.
>
> 3) It's harmless. I don't see an harm in having those bug remained open.
>
> Thanks and regards
> Pulkit
> _______________________________________________
> Mercurial-devel mailing list
> Mercurial-devel at mercurial-scm.org
> https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mercurial-scm.org/pipermail/mercurial-devel/attachments/20190129/4cb776b2/attachment.html>


More information about the Mercurial-devel mailing list