Hi folks,
See below. On Tue, 29 Jan 2019, Pulkit Goyal 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.
I was pointed by Pulkit Goyal to this message, because I was ranting about this on #hg-evolve. I ran into an old bug, which had helpfully been closed, just because it was old. Here is my version, https://bz.mercurial-scm.org/show_bug.cgi?id=6094 I think this is most likely a dupe of this one - https://bz.mercurial-scm.org/show_bug.cgi?id=4202 See mpm's comment in the latter bug, namely It appears this is related to the @ bookmark on the remote repository keeping the obsolete changes visible when they should be hidden. This closely echoes my comment in my bug report, around 5 years later. Anyway, this bug was helpfully closed, and forgotten, with these kinds of lovely automated messages: Bug was inactive for 153 days, archiving Even Pierre-Yves, who was helping me in the channel, and who had actually commented on #4202, seems to have forgotten about it. Frankly, if you want to keep old bugs around, I can hardly think of a better way than by closing the bug reports periodically for no reason. Who thought this, frankly deranged, practice was a good idea, anyway? Regards from an old user. First reported Mercurial bug circa 2005. Faheem Mitha _______________________________________________ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
