(by packager) (beta)

* Release notes

o run git log and, if useful, src/tools/git_topo_order

o run git log and, if useful, src/tools/git_changelog

o update doc/src/sgml/release.sgml

o run spellchecker on result

o add SGML markup

(in addition to the above)

* Release notes

o use git log or src/tools/git_topo_order to find the relevant commits

o use git log or src/tools/git_changelog to find the 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

Creating Back-Branch Release Notes

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

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

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

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

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

require Getopt::Long;

require IPC::Open2;

my@BRANCHES =qw(master REL9_0_STABLE REL8_4_STABLE REL8_3_STABLE

REL8_2_STABLE REL8_1_STABLE REL8_0_STABLE REL7_4_STABLE);

my$timestamp_slop = 600;

my$since;

Getopt::Long::GetOptions('since=s'=> \$since) || usage();

usage()if@ARGV;

my$ts = parse_datetime($c->{'date'});

my$cc;

formy$candidate (@{$all_commits{$ht}}) {

if (abs($ts -$candidate->{'timestamp'}) <600

if (abs($ts -$candidate->{'timestamp'}) <$timestamp_slop

&& !exists$candidate->{'branch_position'}{$c->{'branch'}})

{

$cc =$candidate;

subusage {

printSTDERR<<EOM;

exit 1;

}