Re: [COMMITTERS] pgsql-server/doc/src/sgml Tag: REL7_4_STABLE - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: [COMMITTERS] pgsql-server/doc/src/sgml Tag: REL7_4_STABLE
Date
Msg-id 200312221811.hBMIBDi01746@candle.pha.pa.us
Whole thread Raw
In response to Re: [COMMITTERS] pgsql-server/doc/src/sgml Tag: REL7_4_STABLE  ("Marc G. Fournier" <scrappy@postgresql.org>)
Responses Re: [COMMITTERS] pgsql-server/doc/src/sgml Tag: REL7_4_STABLE  ("Marc G. Fournier" <scrappy@postgresql.org>)
List pgsql-hackers
Marc G. Fournier wrote:
> On Mon, 22 Dec 2003, Bruce Momjian wrote:
> 
> > The only problem with removing HISTORY from CVS is that we will not have
> > an easily reable list of release changes _until_ we package the release.
> > Perhaps we should keep HISTORY in CVS, but regenerate it on tarball
> > packaging, and INSTALL too.
> 
> Confused here, but how "up to date" is HISTORY in CVS to start with?  I
> don't go out of my way to watch for them, but commits to HISTORY don't
> seem to be all that often to start with ... and how many ppl actually look
> at the HISTORY file *except* at release time?

Usually I modify HISTORY during beta, then move it to release.sgml, but
I could reverse that and do edits in release.sgml then regenerate and
copy HISTORY.  It is mostly during beta.  We could throw a URL into the
HISTORY file telling people where to look for the generated release
notes.

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073
 


pgsql-hackers by date:

Previous
From: "Marc G. Fournier"
Date:
Subject: Re: [COMMITTERS] pgsql-server/doc/src/sgml Tag: REL7_4_STABLE
Next
From: Bruce Momjian
Date:
Subject: Re: [COMMITTERS] pgsql-server/doc/src/sgml Tag: REL7_4_STABLE