Based on this discussion I think it is clear the release notes chapter
needs an introductory section. This would not be for any specific
release but the release notes in general. I have come up with the
following text:
The release notes contain the significant changes for each PostgreSQL
release, with major features or migration issues often listed at the
top. The release notes do not contain changes that affect only a few
users or changes that are internal and therefore not user-visible. For
example, the optimizer is improved in almost every release, but the
improvements are usually observed by users as simply faster queries.
A complete list of all changes for a release can only be obtained
by viewing the CVS logs for each release. The committers email
list (http://archives.postgresql.org/pgsql-committers/) contains
all source code changes as well. There is also a web interface
that shows changes to specific files or directories
(http://developer.postgresql.org/cvsweb.cgi/pgsql/). (XXX SVN is
good but needs "Next" button at bottom, no branch filter, https
certificate update
https://projects.commandprompt.com/public/pgsql/log/?action=stop_on_copy&rev=&stop_rev=&mode=stop_on_copy&verbose=on).
A names appearing next to an item represents the major developer for
that item. Of course all changes involve community discussion and patch
review so each item is truely a community activity. First-name-only
entries represent established developers, while full names represent
newer contributors.
I need help with the CVS section. Do we publish full CVS logs for a
release? I like the SVN display because it groups commits but can
improvements I listed above be made?
--
Bruce Momjian <[EMAIL PROTECTED]> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster
