Tom Lane f8d10e50d3 Split the release notes into a separate file for each (active) major branch, ... as per my recent proposal. release.sgml itself is now just a stub that should change rarely; ideally, only once per major release to add a new include line. Most editing work will occur in the release-N.N.sgml files. To update a back branch for a minor release, just copy the appropriate release-N.N.sgml file(s) into the back branch. This commit doesn't change the end-product documentation at all, only the source layout. However, it makes it easy to start omitting ancient information from newer branches' documentation, should we ever decide to do that.		2009-05-02 20:17:57 +00:00
..
FAQ	Replace developer FAQ with a reference to the wiki, which is where	2008-04-22 09:26:39 +00:00
sgml	Split the release notes into a separate file for each (active) major branch,	2009-05-02 20:17:57 +00:00
Makefile	$Header: -> $PostgreSQL Changes ...	2003-11-29 19:52:15 +00:00