Re: Commit fest queue

From: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>
To: Gregory Stark <stark(at)enterprisedb(dot)com>
Cc: Brendan Jurd <direvus(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <bruce(at)momjian(dot)us>, Heikki Linnakangas <heikki(at)enterprisedb(dot)com>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Commit fest queue
Date: 2008-04-10 08:18:12
Message-ID: 47FDCD44.5030004@kaltenbrunner.cc
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Gregory Stark wrote:
> "Brendan Jurd" <direvus(at)gmail(dot)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

this is something that out bugzilla demo installation is actually
capable of (ie it can be entirely driven by and automatically track mail
discussions as long as the mail somehow contains a bugid or get's one
assigned in the course of the discussion).

Stefan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ashish Sharma 2008-04-10 08:27:27 Re: SQL fast in PSQL, very slow using MS.NET driver
Previous Message Csaba Nagy 2008-04-10 08:17:32 Re: Concurrent psql API