From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Neil Conway <neilc(at)samurai(dot)com>, PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: HISTORY fixes |
Date: | 2002-10-02 21:23:27 |
Message-ID: | 200210022123.g92LNRB24236@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
Tom Lane wrote:
> Neil Conway <neilc(at)samurai(dot)com> writes:
> > P.S. Rather than updating HISTORY in one go before we make a release,
> > what does everyone think of the idea of updating HISTORY whenver a
> > patch that makes a user-visible change is committed?
>
> Peter already set up a convention for that: patch the short list near
> the front of doc/src/sgml/release.sgml.
>
> HISTORY is a derived file, really; you should be patching release.sgml
> I think, not HISTORY.
Just a clarification. If you are changing 7.3 stuff, /HISTORY is the
place to do it. If it is prior releases, release.sgml is the place, and
when Peter regenerates HISTORY as part of the final release, /HISTORY is
updated. This is easy to figure out because release.sgml doesn't have
info in it for 7.3 yet.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Justin Clift | 2002-10-02 22:53:07 | Anyone want to assist with the translation of the Advocacy site? |
Previous Message | Tom Lane | 2002-10-02 18:46:36 | Re: HISTORY fixes |