Re: email addresses and the BTS
Michael Stone writes:
> Paul Slootman wrote:
>> How about notification when the bug is closed?
>
> I submit a lot of bugs and it's only rarely that I care about
> getting an email when they're closed. (In most cases I only care
> about the bug when I'm actually running into it. If it's fixed, I'll
> likely not even remember or care about the bug.) If the submitter
> really can't live without the email I guess it would fall under the
> clause I wrote about further personal communication being necessary.
I haven't (yet) checked the bugs affected to see if they're ones I'd
be interested in being notified of fixes or not; I expect there are
some of both kinds.
>> How about when the maintainer wants to ask for additional details
>> on the report? If I ask a submitter for more info, and that email
>> bounces, I will feel inclined to close the bug.
>
> Note that I said "If the bug's been acknowleged". There are some
> cases where the bug is obvious, the maintainer says "yeah, I need to
> fix that" and further emails are not necessary. In that case,
> closing/reopening just to change the email address is just an
> annoyence.
It seems there is no way to win here: if I follow the procedure
described, then the maintainer gets pointless email now, if I don't
then they get bounces later (and may find it difficulty to contact me
if they want more information); and there is no obvious way to
determine which any given maintainer might prefer.
ttfn/rjk
Reply to: