Re: Managing the community information stream

From: "Jim C(dot) Nasby" <decibel(at)decibel(dot)org>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Managing the community information stream
Date: 2007-05-16 15:23:52
Message-ID: 20070516152352.GG14548@nasby.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, May 16, 2007 at 10:46:50AM -0400, Alvaro Herrera wrote:
> > > I am not sure. We will have to investigate more the capabilities of the
> > > bug tracking system we intend to use. In the worst case one could add
> > > the URL for the archived message copy; second worst would be bouncing
> > > (hopefully not forward) the interesting messages to the bug address.
> >
> > Sounds like what I do with the TODO list now.
>
> Except that this is the *worst case* with the bug tracker, whereas for
> the TODO list it is not only the worst case, it is also the best case
> and the only case at all.

And any number of people can manage it (just like the wiki).
--
Jim Nasby decibel(at)decibel(dot)org
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2007-05-16 15:25:01 Re: Integer datetimes
Previous Message David Fetter 2007-05-16 15:19:34 Re: Testing concurrent psql