Skip site navigation (1) Skip section navigation (2)

Re: Getting a bug tracker for the Postgres project

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Greg Stark <gsstark(at)mit(dot)edu>
Cc: Joe Abbate <jma(at)freedomcircle(dot)com>, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Getting a bug tracker for the Postgres project
Date: 2011-05-30 14:28:17
Message-ID: 1306765483-sup-1460@alvh.no-ip.org (view raw or flat)
Thread:
Lists: pgsql-hackers
Excerpts from Greg Stark's message of dom may 29 22:26:21 -0400 2011:

> My ideal bug tracker is the debian one which basically stays out of
> your way and lets you cc any message to a specific bug at
> nnnn(at)bugs(dot)debian(dot)org which archives that message in the bug and sends
> it to anyone listening to the bug. And you can have control commands
> to close it or edit it -- basically making all our existing "that's
> not a bug bleah bleah" messages into "close nnn; that's not a bug
> bleah bleah" messages.

Yeah.  The other good thing about the Debian thing is that email is
first-class citizen; each "bug history" is basically an mbox.  All the
other systems I've looked at try to do the silly thing of extracting
the text from the email and inserting into a "comment" of some sort,
which is ocassionally problematic because of random annoyances in email
messages; and when you want to get down to investigating exactly what
was discussed in the email thread, the interesting bits aren't there.
In the Debian system, you can get the mbox and open it with your
favorite email reading tool instead.

-- 
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

pgsql-hackers by date

Next:From: Joe AbbateDate: 2011-05-30 14:52:51
Subject: Re: Getting a bug tracker for the Postgres project
Previous:From: Tom LaneDate: 2011-05-30 14:21:30
Subject: Re: Nested CASE-WHEN scoping

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group