From 1e0eeab1553117c85b403fa2c427bbb7f247a071 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Wed, 12 Sep 2007 03:21:20 +0000 Subject: [PATCH] Document an efficient way to create documentation for back branches. --- src/tools/RELEASE_CHANGES | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/src/tools/RELEASE_CHANGES b/src/tools/RELEASE_CHANGES index b1ef4931e8..cc7851d36a 100644 --- a/src/tools/RELEASE_CHANGES +++ b/src/tools/RELEASE_CHANGES @@ -60,6 +60,21 @@ For Major Releases * Update inet/cidr data types with newest Bind patches +Creating Back-Branch Release Notes +================================== +* Do 'cvs log' on each back-branch and run pgcvslog + +* Edit and create SGML markup for the most recent branch + +* Make copies of the SGML for each branch, then remove items + that do not apply based on cvs logs for that branch + +* Copy the SGML for each branch into release.sgml in CVS HEAD + +* Copy CVS HEAD release.sgml to each branch and trim off the top + part that doesn't apply for each branch + + --------------------------------------------------------------------------- Library Version Changes