Re: [gentoo-dev] Feedback req: Confirm/thank on bug fix or is that unwanted bug spam?

[Kent Fredric]

On 7/7/07, Duncan <1i5t5.duncan@×××.net> wrote:
> When I open or CC on a bug that then gets fixed, I often feel like adding
> a thanks to the bug.  However, while it may be polite in other
> circumstances, in this case it could be viewed as bug spam, so I've
> hesitated.
>
> I reviewed the bug reporting guidelines a month or so ago and didn't see
> anything either way on it there, so I'm wondering, what's the general
> opinion?  Do you guys appreciate thanks (and confirmation the fix worked
> at the same time, even when it's fairly obvious it should), or would you
> rather not get the spam?
>
> If there's a consensus reached, perhaps it should be added to the bug
> reporting guidelines as well.  I'm sure I'm not the only one who has
> wondered about this.
>
> What I've done occasionally so far is this.  Gentoo tends to leave the
> bug state in resolved/fixed.  When I can confirm it, I'll close the bug,
> with an appropriate note of confirmation and thanks.  Does that work or
> is it still too bug-spammy?  Again, if there's a reasonable consensus,
> it'd be nice to have it mentioned one way or the other in the bug
> reporting guidelines.
>

I /believe/ when you close a bug a notification is sent anyway
irregardless of whether or not you add a comment, but i might be wrong
here.

I myself think dev's should be thanked for their good work and would
like to continue doing so :)

( something has to be done to compensate for the amount of crap i bet
dev's get, recognition occasionally IMO should help them feel loved
and  want to stay here at gentoo :) )

-- 
Kent
ruby -e '[1, 2, 4, 7, 0, 9, 5, 8, 3, 10, 11, 6, 12, 13].each{|x|
print "enNOSPicAMreil kdrtf@×××.com"[(2*x)..(2*x+1)]}'
-- 
gentoo-dev@g.o mailing list