Re: pgFoundry

From: Lamar Owen <lowen(at)pari(dot)edu>
To: Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: pgFoundry
Date: 2005-05-16 18:40:05
Message-ID: 200505161440.05282.lowen@pari.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Monday 16 May 2005 14:12, Robert Treat wrote:
> On Mon, 2005-05-16 at 12:50, Lamar Owen wrote:
> > The only way in my mind to get this dynamism on the website is to make
> > the website part of the process at some level. If someone has to go

> One idea I've tossed around is requiring patches to include release
> notes, and then display the release notes on the web site as a "done so
> far" type of list. It doesn't get you what is under active development,
> but would get you a more up-to-date picture of changes as a release
> evolves.

Well, there is always the '-committers' list; if all CVS commits had/have
meaningful commit changelog notices, then that could drive something.

There are two things being talked about here:
1.) A forward-looking rad map;
2.) A status indication of where development is happening, and a history of
past development.

In my mind 2 is more important than 1, for all the reasons Tom already
mentioned.
--
Lamar Owen
Director of Information Technology
Pisgah Astronomical Research Institute
1 PARI Drive
Rosman, NC 28772
(828)862-5554
www.pari.edu

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeffrey W. Baker 2005-05-16 18:42:35 Re: bitmap scans, btree scans, and tid order
Previous Message Tom Lane 2005-05-16 18:35:19 Re: bitmap scans, btree scans, and tid order