(by packager) (beta)

* Release notes

oscan cvs logs, use pgcvslogand flags in comments

orun git logand, if useful, src/tools/git_topo_order

o update doc/src/sgml/release.sgml

o run spellchecker on result

o add SGML markup

(in addition to the above)

* Release notes

osearch with commit message text to findCVS commit file changes

ouse git log or src/tools/git_topo_order to findthe relevant commits

o check completion of items that have been marked as completed at

http://wiki.postgresql.org/wiki/Todo

o remove completed TODO items

Starting a New Development Cycle

================================

* Create a branch inCVS for maintenance of the previous release

* Create a branch ingit for maintenance of the previous release

* Increment the major version number in src/tools/version_stamp.pl

Creating Back-Branch Release Notes

==================================

*Do 'cvs log' on each back-branch and run pgcvslog

*Run src/tools/git_topo_order to generate a list of relevant commits

*In CVS HEAD, edit and create SGML markup for the most recent branch

in that branch's release-N.N.sgml file

*On the git master branch, edit and create SGML markup for the most recent

branchin that branch's release-N.N.sgml file

* Copy this into older branches' release-N.N.sgml files, then remove

items that do not apply based oncvs logs for that branch (and add

items that do not apply based oncommit logs for that branch (and add

any that are needed)

* Copy the appropriate release-N.N.sgml files into each backCVSbranch

* Copy the appropriate release-N.N.sgml files into each back branch

---------------------------------------------------------------------------