Re: bugs and bug tracking

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: bugs and bug tracking
Date: 2015-10-07 18:32:32
Message-ID: 20151007183232.GI3685@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

* Josh Berkus (josh(at)agliodbs(dot)com) wrote:
> As a serious response, "reply-all" is NOT the default for common GUI
> mail clients (TB, Apple, Gmail, etc.), and I know on TB that it's not
> even possible to make it the default (I miss Kmail). So a system which
> depends on the user ... including outside bug reporters ... always
> hitting "reply all" is going to have some issues.

You mean like our current system?

For starters, unless we start asking our users to submit their gmail
passwords, there's no way to ensure we get all of the emails.

I *really* don't like the idea of rewriting the From/To completely to
force all mail through a relay and I'm pretty sure that "fix" would be
far worse than the problem.

debbugs, as noted previously, does set Reply-To by default, which means
that a user replying to an email (even without reply-all) from debbugs
should have the response go to both the bug and whomever responded to
the initial email.

One thing which can be easily done with debbugs is that someone can
forward or bounce the direct email they receive from the user to the
bug#(at)bugs address and have the info added, if the user removed the bug
email address.

Thanks!

Stephen

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Wagner 2015-10-07 18:35:19 Re: bugs and bug tracking
Previous Message Alvaro Herrera 2015-10-07 18:22:14 Re: bugs and bug tracking