Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-dev
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-dev@g.o
From: Duncan <1i5t5.duncan@...>
Subject: Re: Handling of keywording bugs with only one arch
Date: Sat, 13 Mar 2010 22:43:14 +0000 (UTC)
Samuli Suominen posted on Sat, 13 Mar 2010 19:21:52 +0200 as excerpted:

> On 03/13/2010 07:07 PM, Petteri Räty wrote:
>> When a bug is marked as fixed it doesn't show up in searches developers
>> use so it's a matter of who reads the email and acts upon it. I don't
>> see why maintainers would be any more likely to act than an arch team
>> comprised of multiple people in the case of bigger arches. Let's not
>> forget that users are really supposed to open new bugs instead of
>> commenting on the resolved ones although I know there are users out
>> there who rather comment on a two year old only distantly related bug
>> than open a new one.
> 
> I would love to see a bugzilla feature that would entirely disable
> commenting on closed bugs like on archlinux's bugtracking system[1]
> 
> [1] http://www.mail-archive.com/arch-general@.../msg11996.html
> 
> That might possibly need "Request reopen" button of somesort, or we
> could just always require people to open new bugs
> 
> Often people just wish to argue about the closing status, after the bug
> has been resolved...

Keep in mind that disabling further comments would disable genuine 
followups as well.

There have been a few times where a bug I've filed was closed before I 
found the ultimate cause of the bug (my config or fat-fingering), where I 
leave a comment when I do find the trigger, to hopefully help out others 
who might have the issue later.

There's also the issue of thanks, especially when it was a bug of my own 
causing and the dev took the time to explain what I was doing or had 
failed to do.  Awhile back I asked here if thanks was appropriate in such 
cases, or simply the bother of an extra mail on an already closed bug and 
thus better to skip, and was told go for it, thanks is unfortunately quite 
rare, and thus appreciated because bug squashing can sometimes feel pretty 
thankless, so I've tried to do so tho I can't say I always do.  I'd feel 
quite strange (and expect it would NOT be appreciated, so would simply 
skip it) if I had to open a new bug just to say thanks for fixing the old 
one!

But a note about opening a new bug if it's still an issue and you're not 
the author and therefore can't reopen this one, possibly suggesting bug 
clone, would probably be useful, I agree with petteri/betelgeuse there.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman



References:
Handling of keywording bugs with only one arch
-- Petteri Räty
Re: Handling of keywording bugs with only one arch
-- Jeremy Olexa
Re: Handling of keywording bugs with only one arch
-- Petteri Räty
Re: Handling of keywording bugs with only one arch
-- Samuli Suominen
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: Handling of keywording bugs with only one arch
Next by thread:
Re: Handling of keywording bugs with only one arch
Previous by date:
Re: Re: Reorganizing handling of target specific profiles (Was: Split desktop profile patches & news item for review)
Next by date:
Re: Re: Split desktop profile patches & news item for review


Updated Jun 29, 2012

Summary: Archive of the gentoo-dev mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.