Re: Commit fest queue - Mailing list pgsql-hackers

From Gregory Stark
Subject Re: Commit fest queue
Date
Msg-id 874paaupmq.fsf@oxford.xeocode.com
Whole thread Raw
In response to Re: Commit fest queue  ("Brendan Jurd" <direvus@gmail.com>)
Responses Re: Commit fest queue  (Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>)
Re: Commit fest queue  ("Tom Dunstan" <pgsql@tomd.cc>)
List pgsql-hackers
"Brendan Jurd" <direvus@gmail.com> writes:

> The typical way to solve this is to have the tracker send an automatic
> notification email to a list saying "Hey, there's a new ticket at ,
> come and check it out".

Unfortunately that is the typical way to "solve" this. And it's awful. 
It's like the ubiquitous cryptic phone call in movies saying "can't talk 
right now but there's something you should know. Meet me under the bridge"

Much much better are the systems like debbugs where you get the actual ticket
by email. And can respond by email. And basically never need to visit the web
interface unless you want to see the summarized data.

Personally I would consider any system without at least these attributes to be
unusable:

a) Never sends an email without the full content it's notifying you of

b) Never sends an email which can't be replied to normally

--  Gregory Stark EnterpriseDB          http://www.enterprisedb.com Ask me about EnterpriseDB's Slony Replication
support!


pgsql-hackers by date:

Previous
From: paul rivers
Date:
Subject: Re: Commit fest queue
Next
From: Csaba Nagy
Date:
Subject: Re: Concurrent psql API