Gentoo Archives: gentoo-dev

From: Duncan <1i5t5.duncan@×××.net>
To: gentoo-dev@l.g.o
Subject: [gentoo-dev] Re: Handling of keywording bugs with only one arch
Date: Sat, 13 Mar 2010 22:44:04
Message-Id: pan.2010.03.13.22.43.14@cox.net
In Reply to: Re: [gentoo-dev] Handling of keywording bugs with only one arch by Samuli Suominen
1 Samuli Suominen posted on Sat, 13 Mar 2010 19:21:52 +0200 as excerpted:
2
3 > On 03/13/2010 07:07 PM, Petteri Räty wrote:
4 >> When a bug is marked as fixed it doesn't show up in searches developers
5 >> use so it's a matter of who reads the email and acts upon it. I don't
6 >> see why maintainers would be any more likely to act than an arch team
7 >> comprised of multiple people in the case of bigger arches. Let's not
8 >> forget that users are really supposed to open new bugs instead of
9 >> commenting on the resolved ones although I know there are users out
10 >> there who rather comment on a two year old only distantly related bug
11 >> than open a new one.
12 >
13 > I would love to see a bugzilla feature that would entirely disable
14 > commenting on closed bugs like on archlinux's bugtracking system[1]
15 >
16 > [1] http://www.mail-archive.com/arch-general@×××××××××.org/msg11996.html
17 >
18 > That might possibly need "Request reopen" button of somesort, or we
19 > could just always require people to open new bugs
20 >
21 > Often people just wish to argue about the closing status, after the bug
22 > has been resolved...
23
24 Keep in mind that disabling further comments would disable genuine
25 followups as well.
26
27 There have been a few times where a bug I've filed was closed before I
28 found the ultimate cause of the bug (my config or fat-fingering), where I
29 leave a comment when I do find the trigger, to hopefully help out others
30 who might have the issue later.
31
32 There's also the issue of thanks, especially when it was a bug of my own
33 causing and the dev took the time to explain what I was doing or had
34 failed to do. Awhile back I asked here if thanks was appropriate in such
35 cases, or simply the bother of an extra mail on an already closed bug and
36 thus better to skip, and was told go for it, thanks is unfortunately quite
37 rare, and thus appreciated because bug squashing can sometimes feel pretty
38 thankless, so I've tried to do so tho I can't say I always do. I'd feel
39 quite strange (and expect it would NOT be appreciated, so would simply
40 skip it) if I had to open a new bug just to say thanks for fixing the old
41 one!
42
43 But a note about opening a new bug if it's still an issue and you're not
44 the author and therefore can't reopen this one, possibly suggesting bug
45 clone, would probably be useful, I agree with petteri/betelgeuse there.
46
47 --
48 Duncan - List replies preferred. No HTML msgs.
49 "Every nonfree program has a lord, a master --
50 and if you use the program, he is your master." Richard Stallman