Re: bugs and bug tracking
От | Alvaro Herrera |
---|---|
Тема | Re: bugs and bug tracking |
Дата | |
Msg-id | 20151007182214.GH4405@alvherre.pgsql обсуждение исходный текст |
Ответ на | Re: bugs and bug tracking (Josh Berkus <josh@agliodbs.com>) |
Список | pgsql-hackers |
Josh Berkus wrote: > On 10/07/2015 11:05 AM, Alvaro Herrera wrote: > > Josh Berkus wrote: > >> On 10/07/2015 10:25 AM, Alvaro Herrera wrote: > >>> Hmm, I guess we could have the bug form add > >>> To: NNN@bugs.postgresql.org > >>> CC: pgsql-bugs@postgresql.org > >>> as headers, which should work for most people (since we reply-all), Josh > >>> Berkus being the exception. > >> > >> Well, this will just give you more opportunities to ignore me. > > > > Currently, it just means I have to look harder for stuff you post -- I > > certainly do not ignore you. > > I know, I'm just "Joshing" you. Ah well. > > I worry that in the future it might mean > > your messages don't make it to the "bug threads", if we have such a > > thing. See my followup to Stephen, > > https://www.postgresql.org/message-id/20151007175841.GE4405%40alvherre.pgsql > > where some traffic was not present in the mailing list archives but it > > does appear in the bug report itself. I think we need to make it very > > hard for that to happen, and lack of CCs might become a problem. > > 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. Hm, that's something to keep in mind then when figuring out the detailed specs of the system. -- Álvaro Herrera http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления: