Create a script to handle stamping release version numbers into files,
authorTom Lane <[email protected]>
Tue, 10 Jun 2008 18:09:01 +0000 (18:09 +0000)
committerTom Lane <[email protected]>
Tue, 10 Jun 2008 18:09:01 +0000 (18:09 +0000)
replacing the tedious and error-prone manual process we've been using.

src/tools/RELEASE_CHANGES
src/tools/version_stamp.pl

index 15f26b6323d36d9cb77901090eab12fe16e1c5ce..d501c25ad1d77fce924ee85b2a1b44b75d6227d5 100644 (file)
@@ -2,14 +2,9 @@ For All Releases (major, minor, beta, RC)
 ================
 
 * Release version number changes
-       o doc/bug.template
-       o bump Win32 interface version numbers
-               - src/include/pg_config.h.win32
-               - src/interfaces/libpq/libpq.rc.in
-               - src/port/win32ver.rc
        o update doc/FAQ and doc/src/FAQ/FAQ.html
        o copy FAQs from HEAD to top-most branch
-       o configure.in, and run autoconf or update configure (by packager)
+       o run src/tools/version_stamp.pl, then run autoconf (by packager)
 
 * Release notes
        o scan cvs logs, use pgcvslog and flags in comments
index f42d970ac5776876cd4193d7ed247d1e8b942679..e8c8b664f42186d428b6fde2458e00addee25a73 100755 (executable)
@@ -23,7 +23,7 @@
 # Major version is hard-wired into the script.  We update it when we branch
 # a new development version.
 $major1 = 8;
-$major2 = 4;
+$major2 = 2;
 
 # Validate argument and compute derived variables
 $minor = shift;