Log Message:
-----------
Add in a step to release checklist, to verify that the function
upgradeSchema() (src/backend/slony1_funcs.sql) has all the latest sets of
Slony-I versions.

Modified Files:
--------------
    slony1-engine/doc/adminguide:
        releasechecklist.sgml (r1.6 -> r1.7)

-------------- next part --------------
Index: releasechecklist.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/releasechecklist.sgml,v
retrieving revision 1.6
retrieving revision 1.7
diff -Ldoc/adminguide/releasechecklist.sgml -Ldoc/adminguide/releasechecklist.sgml -u -w -r1.6 -r1.7
--- doc/adminguide/releasechecklist.sgml
+++ doc/adminguide/releasechecklist.sgml
@@ -78,6 +78,14 @@
 <filename>configure</filename>; we shouldn't be tracking this in CVS.
 </para>
 
+<listitem><para> One test that seems inherently troublesome to
+automate is the set of version numbers listed in upgradeSchema() in
+src/backend/slony1_funcs.sql. </para>
+
+<para> As new versions are released, the lists of version numbers will
+need to get changed; this does not seem amenable to much
+automation. </para> </listitem>
+
 <listitem><para>make sure that the generated files from .l and .y are
 created, for example <filename>slony/conf-file.[ch]</filename> </para>