Re: Maintaining the list of release changes

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Maintaining the list of release changes
Date: 2002-02-08 21:03:39
Message-ID: 7301.1013202219@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
>> I think I prefer the file-of-notes idea, but this is a possibility worth
>> suggesting.

> We can do whatever people want. I was just afraid it would be too much
> work for people, and I am willing to continue doing it. Actually, if
> people want to help, looking over the final is 10x more valuable than
> having a separate file, at least for me.

Even if people do review the notes, who's to say they'll remember a
change they made months ago? I think it's important for developers to
prepare at least a rough-draft entry for the release notes at the time
the change is made. We can debate different ways to keep that info
available until the docs are prepared, but the real problem here is to
not rely on memory.

regards, tom lane

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Darren Johnson 2002-02-08 21:11:43 Re: Replication
Previous Message Tom Lane 2002-02-08 20:58:04 Re: compile error of PostgreSQL 7.2 on FreeBSD-current