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 PostgreSQLrelease, with major features or migration issues
oftenlisted at thetop. The release notes do not contain changes that affect only a fewusers or changes that are
internaland therefore not user-visible. Forexample, the optimizer is improved in almost every release, but
theimprovementsare usually observed by users as simply faster queries.
A complete list of all changes for a release can only be obtainedby viewing the CVS logs for each release. The
committersemaillist (http://archives.postgresql.org/pgsql-committers/) containsall source code changes as well. There
isalso a web interfacethat shows changes to specific files or
directories(http://developer.postgresql.org/cvsweb.cgi/pgsql/). (XXX SVN isgood but needs "Next" button at bottom, no
branchfilter, httpscertificate
updatehttps://projects.commandprompt.com/public/pgsql/log/?action=stop_on_copy&rev=&stop_rev=&mode=stop_on_copy&verbose=on).A
namesappearing next to an item represents the major developer forthat item. Of course all changes involve community
discussionand patchreview so each item is truely a community activity. First-name-onlyentries represent established
developers,while full names representnewer 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 <bruce@momjian.us> http://momjian.us EnterpriseDB
http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
