Re: [HACKERS] 7.5 change documentation

2004-02-02 Thread Tom Lane
"Simon Riggs" <[EMAIL PROTECTED]> writes: > Could you help me by suggesting where/how to update it (would it be in > the CVS, or do you want me to just e-mail you/somebody the file?) and > what format would work best (text, HTML, docbook). Seems like the way to work this is to keep it on a webpage

Re: [HACKERS] 7.5 change documentation

2004-02-02 Thread Simon Riggs
>Bruce Momjian > Richard Huxton wrote: > > On Wednesday 28 January 2004 00:38, Simon Riggs wrote: > > > POSTGRESQL: Summary of Changes since last release (7.4.1) > > > > > All corrections and changes welcome...if this is well received, then I > > > will monitor pgsql-commiters to keep track of thin

Re: [HACKERS] 7.5 change documentation

2004-01-30 Thread Bruce Momjian
Richard Huxton wrote: > On Wednesday 28 January 2004 00:38, Simon Riggs wrote: > > POSTGRESQL: Summary of Changes since last release (7.4.1) > > > All corrections and changes welcome...if this is well received, then I > > will monitor pgsql-commiters to keep track of things. > > Speaking as Just

Re: [HACKERS] 7.5 change documentation

2004-01-28 Thread Richard Huxton
On Wednesday 28 January 2004 00:38, Simon Riggs wrote: > POSTGRESQL: Summary of Changes since last release (7.4.1) > All corrections and changes welcome...if this is well received, then I > will monitor pgsql-commiters to keep track of things. Speaking as JustAUser (TM) I find this very useful.

Re: [HACKERS] 7.5 change documentation

2004-01-27 Thread Simon Riggs
POSTGRESQL: Summary of Changes since last release (7.4.1) -- 26 Jan 2004 This is a summary of most changes since code versions marked 7_4_1, rather than a weekly news bulletin, a summary of desired future items, or the definitive list of what

Re: [HACKERS] 7.5 change documentation

2004-01-26 Thread Bruce Momjian
Tom Lane wrote: > Neil Conway <[EMAIL PROTECTED]> writes: > It's fine with me if Bruce prefers to build the release notes directly > from the change logs. As I saw it, the purpose of the temporary list of > things-done-so-far is not to be the raw material for the release notes. > It's to let alpha

Re: [HACKERS] 7.5 change documentation

2004-01-26 Thread Simon Riggs
OK, I will attempt to draw together this information as currently stands. If this makes any sense, we can discuss what the requirement/process is for regular maintenance (daily/weekly/monthly etc). Understood to mean "changes in next release (current progress)" - items that have been completed/com

Re: [HACKERS] 7.5 change documentation

2004-01-23 Thread Tom Lane
Neil Conway <[EMAIL PROTECTED]> writes: > Tom Lane <[EMAIL PROTECTED]> writes: >> In theory there should be a section at the head of release.sgml >> mentioning the major changes done-so-far, but for various reasons >> this hasn't gotten installed in the 7.5 branch yet. (Look at the >> CVS versions

Re: [HACKERS] 7.5 change documentation

2004-01-23 Thread Neil Conway
Tom Lane <[EMAIL PROTECTED]> writes: > In theory there should be a section at the head of release.sgml > mentioning the major changes done-so-far, but for various reasons > this hasn't gotten installed in the 7.5 branch yet. (Look at the > CVS versions during 7.4 development to see how we did it l